Merge pull request #177445 from alexbuckgit/alexbuckgit/docutune-autopr-20211025-193844-2965520

jborsecnik · web-flow · commit 980139afc349 · 2021-10-25T14:55:39.000-07:00
DocuTune: Fix or remove abbreviations
diff --git a/articles/active-directory-b2c/partner-f5.md b/articles/active-directory-b2c/partner-f5.md
@@ -59,7 +59,7 @@ The secure hybrid access solution for this scenario is made up of the following
 
 - **Application** - Backend service being protected by Azure AD B2C and BIG-IP secure hybrid access
 
-- **Azure AD B2C** - The IdP and Open ID Connect (OIDC) authorization server, responsible for verification of user credentials, multi-factor authentication (MFA), and SSO to the BIG-IP APM.
+- **Azure AD B2C** - The IdP and Open ID Connect (OIDC) authorization server, responsible for verification of user credentials, multifactor authentication (MFA), and SSO to the BIG-IP APM.
 
 - **BIG-IP** - As the reverse proxy for the application, the BIG-IP APM also becomes the OIDC client, delegating authentication to the OIDC authorization server, before performing header-based SSO to the backend service.
 
@@ -222,9 +222,9 @@ Here, we'll configure Azure AD B2C as the OAuth2 IdP. You’ll notice that the G
 
   |Properties | Descriptions|
   |:---------|:---------|
-  | Client ID | The client ID of the application representing the BIG-IP in your Azure AD B2C tenant.|
+  | Client ID | The client ID of the application representing the BIG-IP in your Azure AD B2C tenant. |
   | Client secret | The application’s corresponding client secret. |
-  |Client-server SSL profile | Setting an SSL profile will ensure the APM communicates with the Azure AD B2C IdP over TLS. Select the default serverssl option.|
+  |Client-server SSL profile | Setting an SSL profile will ensure the APM communicates with the Azure AD B2C IdP over TLS. Select the default `serverssl` option. |
 
 - **OAuth request settings**
 
@@ -281,7 +281,7 @@ Here, we'll configure Azure AD B2C as the OAuth2 IdP. You’ll notice that the G
   | Service port | HTTPS |
   | Enable redirect port | Check to have users auto redirected from http to https |
   | Redirect port | HTTP |
-  | Client SSL profile | Swap the pre-defined clientssl profile with the one containing your SSL certificate. Testing with the default profile is also ok but will likely cause a browser alert.|
+  | Client SSL profile | Swap the predefined `clientssl` profile with the one containing your SSL certificate. Testing with the default profile is also ok but will likely cause a browser alert. |
 
 - **Pool properties**
 
diff --git a/articles/active-directory/cloud-sync/tutorial-pilot-aadc-aadccp.md b/articles/active-directory/cloud-sync/tutorial-pilot-aadc-aadccp.md
@@ -198,7 +198,7 @@ Azure AD Connect sync synchronizes changes occurring in your on-premises directo
 >[!NOTE] 
 >If you are running your own custom scheduler for Azure AD Connect sync, then please enable the scheduler. 
 
-Once the scheduler is enabled, Azure AD Connect will stop exporting any changes on objects with `cloudNoFlow=true` in the metaverse, unless any reference attribute (eg. manager) is being updated. In case there is any reference attribute update on the object, Azure AD Connect will ignore the `cloudNoFlow` signal and export all updates on the object.
+Once the scheduler is enabled, Azure AD Connect will stop exporting any changes on objects with `cloudNoFlow=true` in the metaverse, unless any reference attribute (such as `manager`) is being updated. In case there is any reference attribute update on the object, Azure AD Connect will ignore the `cloudNoFlow` signal and export all updates on the object.
 
 ## Something went wrong
 In case the pilot does not work as expected, you can go back to the Azure AD Connect sync setup by following the steps below:
diff --git a/articles/active-directory/conditional-access/terms-of-use.md b/articles/active-directory/conditional-access/terms-of-use.md
@@ -41,7 +41,7 @@ Azure AD terms of use policies have the following capabilities:
 - Require employees or guests to accept your terms of use policy prior to registering security information in Azure AD Multi-Factor Authentication (MFA).
 - Require employees to accept your terms of use policy prior to registering security information in Azure AD self-service password reset (SSPR).
 - Present a general terms of use policy for all users in your organization.
-- Present specific terms of use policies based on a user attributes (ex. doctors vs nurses or domestic vs international employees, by using [dynamic groups](../enterprise-users/groups-dynamic-membership.md)).
+- Present specific terms of use policies based on a user attributes (such as doctors versus nurses, or domestic versus international employees) by using [dynamic groups](../enterprise-users/groups-dynamic-membership.md)).
 - Present specific terms of use policies when accessing high business impact applications, like Salesforce.
 - Present terms of use policies in different languages.
 - List who has or hasn't accepted to your terms of use policies.
diff --git a/articles/active-directory/manage-apps/f5-bigip-deployment-guide.md b/articles/active-directory/manage-apps/f5-bigip-deployment-guide.md
@@ -42,9 +42,9 @@ Prior F5 BIG-IP experience or knowledge isn't necessary, however, we do recommen
 
 - A wildcard or Subject Alternative Name (SAN) certificate, to publish web applications over Secure Socket Layer (SSL). [Let’s encrypt](https://letsencrypt.org/) offers free 90 days certificate for  testing.
 
-- An SSL certificate for securing the BIG-IPs management interface. A certificate used to publish web apps can be used, if its subject corresponds to the BIG-IP's Fully qualified domain name (FQDN). For example, a wildcard certificate defined with a subject *.contoso.com would be suitable for `https://big-ip-vm.contoso.com:8443`
+- An SSL certificate for securing the BIG-IPs management interface. A certificate used to publish web apps can be used, if its subject corresponds to the BIG-IP's Fully qualified domain name (FQDN). For example, a wildcard certificate defined with a subject `*.contoso.com` would be suitable for `https://big-ip-vm.contoso.com:8443`
 
-VM deployment and base system configs take approx. 30 minutes, at which point your BIG-IP platform will be ready for implementing any of the SHA scenarios listed [here](f5-aad-integration.md).
+VM deployment and base system configs take approximately 30 minutes, at which point your BIG-IP platform will be ready for implementing any of the SHA scenarios listed in [Integrate F5 BIG-IP with Azure Active Directory](f5-aad-integration.md).
 
 For testing the scenarios, this tutorial assumes the BIG-IP will be deployed into an Azure resource group containing an Active Directory (AD) environment. The environment should consist of a Domain Controller (DC) and web host (IIS) VMs. Having these servers in other locations to the BIG-IP VM is also ok, providing the BIG-IP has line of sight to each of the roles required to support a given scenario. Scenarios where the BIG-IP VM is connected to another environment over a VPN connection are also supported.
 
@@ -230,7 +230,7 @@ The following steps assume the DNS zone of the public domain used for your SHA s
   If you manage your DNS domain namespace using an external provider like [GoDaddy](https://www.godaddy.com/), then you'll need to create records using their own DNS management facility.
 
 >[!NOTE]
->You can also use a PC’s local hosts file if testing and frequently switching DNS records. The localhosts file on a Windows PC can be accessed by pressing Win + R on the keyboard and submitting the word **drivers** in the run box. Just be mindful that a localhost record will only provide DNS resolution for the local PC, not other clients.
+>You can also use a PC’s local hosts file if testing and frequently switching DNS records. The local hosts file on a Windows PC can be accessed by pressing Win + R on the keyboard and entering *drivers* in the **Run** box. Just be mindful that a local host record will only provide DNS resolution for the local PC, not other clients.
 
 ## Client traffic
 
@@ -351,15 +351,15 @@ Provisioning both, Client and Server SSL profiles will have the BIG-IP pre-confi
 
 2. From the **Import Type** drop down list, select **PKCS 12(IIS)**
 
-3. Provide a name for the imported certificate, for example,  `ContosoWilcardCert`
+3. Provide a name for the imported certificate, such as `ContosoWildcardCert`.
 
 4. Select **Choose File** to browse to the SSL web certificate who’s subject name corresponds to the domain suffix you plan on using for published services
 
 5. Provide the **password** for the imported certificate then select **Import**
 
 6. From the left-navigation bar, go to **Local Traffic** > **Profiles** > **SSL** > **Client** and then select **Create**
 
-7. In the **New Client SSL Profile** page, provide a unique friendly name for the new client SSL profile and ensure the Parent profile is set to **clientssl**
+7. In the **New Client SSL Profile** page, provide a unique friendly name for the new client SSL profile and ensure the Parent profile is set to `clientssl`.
 
 ![The image shows update big-ip](./media/f5ve-deployment-plan/client-ssl.png)
 
@@ -371,7 +371,7 @@ Provisioning both, Client and Server SSL profiles will have the BIG-IP pre-confi
 
 10.	Repeat steps 6-9 to create an **SSL server certificate profile**. From the top ribbon, select **SSL** > **Server** > **Create**.
 
-11.	In the **New Server SSL Profile** page, provide a unique friendly name for the new server SSL profile and ensure the Parent profile is set to **serverssl**
+11.	In the **New Server SSL Profile** page, provide a unique friendly name for the new server SSL profile and ensure the Parent profile is set to `serverssl`.
 
 12.	Select the far-right check box for the Certificate and Key rows and from the drop-down list select your imported certificate, followed by **Finished**.
 
diff --git a/articles/azure-monitor/visualize/workbooks-tile-visualizations.md b/articles/azure-monitor/visualize/workbooks-tile-visualizations.md
@@ -101,7 +101,7 @@ The author has an option to set the tile width in the tile settings.
 
 * `fixed` (default)
 
-    The default behavior of tiles is to be the same fixed width, approx. 160 pixels wide, plus the space around the tiles.
+    The default behavior of tiles is to be the same fixed width, approximately 160 pixels wide, plus the space around the tiles.
 
     ![Screenshot displaying fixed width tiles](./media/workbooks-tile-visualizations/tiles-fixed.png)
 * `auto`
diff --git a/articles/cosmos-db/how-to-setup-cmk.md b/articles/cosmos-db/how-to-setup-cmk.md
@@ -358,7 +358,7 @@ When using customer-managed keys, [Request Units](./request-units.md) consumed b
 | Operation type | Request Unit increase |
 |---|---|
 | Point-reads (fetching items by their ID) | + 5% per operation |
-| Any write operation | + 6% per operation<br/>approx. + 0.06 RU per indexed property |
+| Any write operation | + 6% per operation <br/> Approximately + 0.06 RU per indexed property |
 | Queries, reading change feed, or conflict feed | + 15% per operation |
 
 ### What data gets encrypted with the customer-managed keys?
diff --git a/articles/hdinsight/spark/apache-spark-create-standalone-application.md b/articles/hdinsight/spark/apache-spark-create-standalone-application.md
@@ -31,7 +31,7 @@ In this tutorial, you learn how to:
 
 * [Oracle Java Development kit](https://www.azul.com/downloads/azure-only/zulu/).  This tutorial uses Java version 8.0.202.
 
-* A Java IDE. This article uses [IntelliJ IDEA Community ver.  2018.3.4](https://www.jetbrains.com/idea/download/).
+* A Java IDE. This article uses [IntelliJ IDEA Community 2018.3.4](https://www.jetbrains.com/idea/download/).
 
 * Azure Toolkit for IntelliJ.  See [Installing the Azure Toolkit for IntelliJ](/java/azure/intellij/azure-toolkit-for-intellij-create-hello-world-web-app#installation-and-sign-in).
 
@@ -223,7 +223,7 @@ If you're not going to continue to use this application, delete the cluster that
 
 1. Select **Delete**. Select **Yes**.
 
-:::image type="content" source="./media/apache-spark-create-standalone-application/hdinsight-azure-portal-delete-cluster.png" alt-text="HDInsight azure portal delete cluster" border="true":::
+:::image type="content" source="./media/apache-spark-create-standalone-application/hdinsight-azure-portal-delete-cluster.png" alt-text="Screenshot showing how to delete an HDInsight cluster via the Azure portal." border="true":::
 
 ## Next step
 
diff --git a/articles/hdinsight/spark/apache-spark-intellij-tool-failure-debug.md b/articles/hdinsight/spark/apache-spark-intellij-tool-failure-debug.md
@@ -17,7 +17,7 @@ This article provides step-by-step guidance on how to use HDInsight Tools in [Az
 
 * [Oracle Java Development kit](https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html). This tutorial uses Java version 8.0.202.
   
-* IntelliJ IDEA. This article uses [IntelliJ IDEA Community ver. 2019.1.3](https://www.jetbrains.com/idea/download/#section=windows).
+* IntelliJ IDEA. This article uses [IntelliJ IDEA Community 2019.1.3](https://www.jetbrains.com/idea/download/#section=windows).
   
 * Azure Toolkit for IntelliJ. See [Installing the Azure Toolkit for IntelliJ](/azure/developer/java/toolkit-for-intellij/installation).
 
diff --git a/articles/hdinsight/spark/apache-spark-intellij-tool-plugin.md b/articles/hdinsight/spark/apache-spark-intellij-tool-plugin.md
@@ -29,7 +29,7 @@ In this article, you learn how to:
 
 * [Oracle Java Development kit](https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html).  This article uses Java version 8.0.202.
 
-* IntelliJ IDEA. This article uses [IntelliJ IDEA Community ver.  2018.3.4](https://www.jetbrains.com/idea/download/).
+* IntelliJ IDEA. This article uses [IntelliJ IDEA Community 2018.3.4](https://www.jetbrains.com/idea/download/).
 
 * Azure Toolkit for IntelliJ.  See [Installing the Azure Toolkit for IntelliJ](/azure/developer/java/toolkit-for-intellij/).
 
diff --git a/articles/virtual-machines/linux/openshift-container-platform-3x.md b/articles/virtual-machines/linux/openshift-container-platform-3x.md
@@ -277,7 +277,7 @@ Different releases may have different parameters so verify the necessary paramet
 | `domainName` | Name of the custom domain name to use (if applicable). Set to "none" if not deploying fully private cluster |  | none |
 | `masterClusterDnsType` | Domain type for OpenShift web console. 'default' will use DNS label of master infra public IP. 'custom' allows you to define your own name | default <br> custom | default |
 | `masterClusterDns` | The custom DNS name to use to access the OpenShift web console if you selected 'custom' for `masterClusterDnsType` |  | console.contoso.com |
-| `routingSubDomainType` | If set to 'nipio', `routingSubDomain` will use nip.io.  Use 'custom' if you have your own domain that you want to use for routing | nipio <br> custom | nipio |
+| `routingSubDomainType` | If set to `nipio`, `routingSubDomain` will use `nip.io`.  Use 'custom' if you have your own domain that you want to use for routing | `nipio` <br> custom | `nipio` |
 | `routingSubDomain` | The wildcard DNS name you want to use for routing if you selected 'custom' for `routingSubDomainType` |  | apps.contoso.com |
 | `virtualNetworkNewOrExisting` | Select whether to use an existing Virtual Network or create a new Virtual Network | existing <br> new | new |
 | `virtualNetworkResourceGroupName` | Name of the Resource Group for the new Virtual Network if you selected 'new' for `virtualNetworkNewOrExisting` |  | resourceGroup().name |
diff --git a/articles/virtual-machines/workloads/hpc/compiling-scaling-applications.md b/articles/virtual-machines/workloads/hpc/compiling-scaling-applications.md
@@ -87,14 +87,14 @@ $ gfortran [gFortran flags]
 ```
    
 ### PGI Compiler
-PGI Community Edition ver. 17 is confirmed to work with AMD EPYC. A PGI-compiled version of STREAM does deliver full memory bandwidth of the platform. The newer Community Edition 18.10 (Nov 2018) should likewise work well. Below is sample CLI to compiler optimally with the Intel Compiler:
+PGI Community Edition 17 is confirmed to work with AMD EPYC. A PGI-compiled version of STREAM does deliver full memory bandwidth of the platform. The newer Community Edition 18.10 (Nov 2018) should likewise work well. Below is sample CLI to compiler optimally with the Intel Compiler:
 
 ```bash
 pgcc $(OPTIMIZATIONS_PGI) $(STACK) -DSTREAM_ARRAY_SIZE=800000000 stream.c -o stream.pgi
 ```
 
 ### Intel Compiler
-Intel Compiler ver. 18 is confirmed to work with AMD EPYC. Below is sample CLI to compiler optimally with the Intel Compiler.
+Intel Compiler 18 is confirmed to work with AMD EPYC. Below is sample CLI to compiler optimally with the Intel Compiler.
 
 ```bash
 icc -o stream.intel stream.c -DSTATIC -DSTREAM_ARRAY_SIZE=800000000 -mcmodel=large -shared-intel -Ofast –qopenmp
