diff --git a/docs/azure/sdk/includes/assign-local-dev-group-to-role-azure-portal-4.md b/docs/azure/sdk/includes/assign-local-dev-group-to-role-azure-portal-4.md index 1ff15830a2eb4..e8084693c7dc0 100644 --- a/docs/azure/sdk/includes/assign-local-dev-group-to-role-azure-portal-4.md +++ b/docs/azure/sdk/includes/assign-local-dev-group-to-role-azure-portal-4.md @@ -2,5 +2,5 @@ The *Add role assignment* page lists all of the roles that can be assigned for t 1. Use the search box to filter the list to a more manageable size. This example shows how to filter for Storage Blob roles. 1. Select the role that you want to assign. -
+ Select *Next* to go to the next screen. diff --git a/docs/azure/sdk/includes/assign-managed-identity-to-role-azure-portal-4.md b/docs/azure/sdk/includes/assign-managed-identity-to-role-azure-portal-4.md index 1ff15830a2eb4..e8084693c7dc0 100644 --- a/docs/azure/sdk/includes/assign-managed-identity-to-role-azure-portal-4.md +++ b/docs/azure/sdk/includes/assign-managed-identity-to-role-azure-portal-4.md @@ -2,5 +2,5 @@ The *Add role assignment* page lists all of the roles that can be assigned for t 1. Use the search box to filter the list to a more manageable size. This example shows how to filter for Storage Blob roles. 1. Select the role that you want to assign. -
+ Select *Next* to go to the next screen. diff --git a/docs/azure/sdk/includes/assign-service-principal-to-role-azure-portal-4.md b/docs/azure/sdk/includes/assign-service-principal-to-role-azure-portal-4.md index 1ff15830a2eb4..e8084693c7dc0 100644 --- a/docs/azure/sdk/includes/assign-service-principal-to-role-azure-portal-4.md +++ b/docs/azure/sdk/includes/assign-service-principal-to-role-azure-portal-4.md @@ -2,5 +2,5 @@ The *Add role assignment* page lists all of the roles that can be assigned for t 1. Use the search box to filter the list to a more manageable size. This example shows how to filter for Storage Blob roles. 1. Select the role that you want to assign. -
+ Select *Next* to go to the next screen. diff --git a/docs/core/compatibility/core-libraries/5.0/code-access-security-apis-obsolete.md b/docs/core/compatibility/core-libraries/5.0/code-access-security-apis-obsolete.md index cbd99fdcc057f..5145586ea3ea9 100644 --- a/docs/core/compatibility/core-libraries/5.0/code-access-security-apis-obsolete.md +++ b/docs/core/compatibility/core-libraries/5.0/code-access-security-apis-obsolete.md @@ -428,7 +428,7 @@ Due to CAS's deprecation, the [supporting infrastructure was not brought forward - `T:System.Security.Permissions.WebBrowserPermissionLevel` - `T:System.Security.Permissions.ZoneIdentityPermission` - `T:System.Security.Permissions.ZoneIdentityPermissionAttribute` -- `M:`System.Security.Policy.ApplicationTrust.ApplicationTrust(PermissionSet, IEnumerable)` +- `M:System.Security.Policy.ApplicationTrust.ApplicationTrust(PermissionSet, IEnumerable)` - `P:System.Security.Policy.ApplicationTrust.FullTrustAssemblies` - `T:System.Security.Policy.FileCodeGroup` - `T:System.Security.Policy.GacInstalled` diff --git a/docs/core/extensions/windows-service.md b/docs/core/extensions/windows-service.md index 388702cccc1a9..1e998b93aed0c 100644 --- a/docs/core/extensions/windows-service.md +++ b/docs/core/extensions/windows-service.md @@ -174,7 +174,7 @@ For more information on registering services, see [Dependency injection in .NET] To create the .NET Worker Service app as a Windows Service, it's recommended that you publish the app as a single file executable. It's less error-prone to have a self-contained executable, as there aren't any dependent files lying around the file system. But you may choose a different publishing modality, which is perfectly acceptable, so long as you create an **.exe* file that can be targeted by the Windows Service Control Manager. > [!IMPORTANT] -> An alternative publishing approach is to build the **.dll* (instead of an **.exe*), and when you install the published app using the Windows Service Control Manager you delegate to the .NET CLI and pass the DLL. For more information, see [.NET CLI: dotnet command](../tools/dotnet.md). +> An alternative publishing approach is to build the *\*.dll* (instead of an *\*.exe*), and when you install the published app using the Windows Service Control Manager you delegate to the .NET CLI and pass the DLL. For more information, see [.NET CLI: dotnet command](../tools/dotnet.md). > > ```powershell > sc.exe create ".NET Joke Service" binpath="C:\Path\To\dotnet.exe C:\Path\To\App.WindowsService.dll" diff --git a/docs/devops/github-actions-overview.md b/docs/devops/github-actions-overview.md index 2fd50d7fffd87..137917b950b8e 100644 --- a/docs/devops/github-actions-overview.md +++ b/docs/devops/github-actions-overview.md @@ -29,7 +29,7 @@ While there are plenty of GitHub Actions available in the [Marketplace](https:// ## Workflow file -GitHub Actions are utilized through a workflow file. The workflow file must be located in the *.github/workflows* directory of the repository, and is expected to be YAML (either **.yml* or **.yaml*). Workflow files define the *workflow composition*. A workflow is a configurable automated process made up of one or more jobs. For more information, see [Workflow syntax for GitHub Actions](https://docs.github.com/actions/reference/workflow-syntax-for-github-actions). +GitHub Actions are utilized through a workflow file. The workflow file must be located in the *.github/workflows* directory of the repository, and is expected to be YAML (either *\*.yml* or *\*.yaml*). Workflow files define the *workflow composition*. A workflow is a configurable automated process made up of one or more jobs. For more information, see [Workflow syntax for GitHub Actions](https://docs.github.com/actions/reference/workflow-syntax-for-github-actions). ### Example workflow files