Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into content-pattern-and-metadata-edits-for-app-service-375898

Author: ShawnJackson

articles/active-directory-b2c/identity-provider-apple-id.md

@@ -110,7 +110,7 @@ If the sign-in process is successful, your browser is redirected to `https://jwt
 
 ## Signing the client secret
 
-Use the .p8 file you downloaded previously to sign the client secret into a JWT token. There are many libraries that can create and sign the JWT for you. Use the [Azure Function that creates a token](https://github.com/azure-ad-b2c/samples/tree/master/policies/sign-in-with-apple/azure-function) for you. 
+Use the .p8 file you downloaded previously to sign the client secret into a JWT. There are many libraries that can create and sign the JWT for you. Use the [Azure Function that creates a token](https://github.com/azure-ad-b2c/samples/tree/master/policies/sign-in-with-apple/azure-function) for you. 
 
 1. Create an [Azure Function](../azure-functions/functions-create-function-app-portal.md).
 1. Under **Developer**, select **Code + Test**. 
@@ -154,7 +154,7 @@ You need to store the client secret that you previously recorded in your Azure A
 1. Select **Policy Keys**, and then select **Add**.
 1. For **Options**, choose **Manual**.
 1. Enter a **Name** for the policy key. For example, "AppleSecret". The prefix "B2C_1A_" is added automatically to the name of your key.
-1. In **Secret**, enter the value of a token returned by the Azure Function (a JWT token).
+1. In **Secret**, enter the value of a token returned by the Azure Function (a JWT).
 1. For **Key usage**, select **Signature**.
 1. Select **Create**.
 

articles/active-directory-b2c/session-behavior.md

@@ -317,9 +317,9 @@ The following example illustrates the JWT and SAML token issuers with single sig
 <ClaimsProvider>
   <DisplayName>Local Account SignIn</DisplayName>
   <TechnicalProfiles>
-    <!-- JWT Token Issuer -->
+    <!-- JWT Issuer -->
     <TechnicalProfile Id="JwtIssuer">
-      <DisplayName>JWT token Issuer</DisplayName>
+      <DisplayName>JWT Issuer</DisplayName>
       <Protocol Name="OpenIdConnect" />
       <OutputTokenFormat>JWT</OutputTokenFormat>
       ...    

articles/active-directory-b2c/troubleshoot.md

@@ -155,11 +155,11 @@ The following screenshot shows an example of the Application Insights trace log
 
 ![Screenshot of Azure AD B2C extension Azure AD B2C trace report.](./media/troubleshoot-custom-policies/vscode-extension-application-insights-report.png)
 
-## Troubleshoot JWT tokens
+## Troubleshoot JWTs
 
-For JWT token validation and debugging purposes, your can decode JWTs using a site like [https://jwt.ms](https://jwt.ms). Create a test application that can redirect to `https://jwt.ms` for token inspection. If you haven't already done so, [register a web application](tutorial-register-applications.md), and [enable ID token implicit grant](tutorial-register-applications.md#enable-id-token-implicit-grant). 
+For JWT validation and debugging purposes, your can decode JWTs using a site like [https://jwt.ms](https://jwt.ms). Create a test application that can redirect to `https://jwt.ms` for token inspection. If you haven't already done so, [register a web application](tutorial-register-applications.md), and [enable ID token implicit grant](tutorial-register-applications.md#enable-id-token-implicit-grant). 
 
-![Screenshot of JWT token preview.](./media/troubleshoot-custom-policies/jwt-token-preview.png)
+![Screenshot of JWT preview.](./media/troubleshoot-custom-policies/jwt-token-preview.png)
 
 Use **Run now** and `https://jwt.ms` to test your policies independently of your web or mobile application. This website acts like a relying party application. It displays the contents of the JSON web token (JWT) that your Azure AD B2C policy generates.
 

articles/app-service/monitor-instances-health-check.md

@@ -143,11 +143,11 @@ function envVarMatchesHeader(headerValue) {
 
 ## Instances
 
-Once Health check is enabled, you can restart and monitor the status of your application instances from the instances tab. The instances tab shows your instance's name and the status of that application's instance. You can also manually restart the instance from this tab.
+Once Health check is enabled, you can restart and monitor the status of your application instances from the instances tab. The instances tab shows your instance's name and the status of that application's instance. You can also manually do an advanced application restart from this tab by using the "Restart" button.
 
-If the status of your application instance is "unhealthy," you can restart the instance manually by using the restart button in the table. Keep in mind that any other applications hosted on the same App Service plan as the instance will also be affected by the restart. If there are other applications using the same App Service plan as the instance, they're listed on the opening blade from the restart button.
+If the status of your application instance is "unhealthy," you can restart the worker process of the respective app manually by using the restart button in the table. This will not be affecting any of the other applications hosted on the same App Service plan. If there are other applications using the same App Service plan as the instance, they're listed on the opening blade from the restart button.
 
-If you restart the instance and the restart process fails, you'll be given the option to replace the worker. (Only one instance can be replaced per hour.)  This will also affect any applications using the same App Service plan.
+If you restart the instance and the restart process fails, you'll be given the option to replace the worker. (Only one instance can be replaced per hour.)  This will affect any applications using the same App Service plan.
 
 For Windows applications, you can also view processes via the Process Explorer. This gives you further insight on the instance's processes, including thread count, private memory, and total CPU time.
 

articles/azure-cache-for-redis/cache-high-availability.md

@@ -132,10 +132,7 @@ Zone-redundant Enterprise and Enterprise Flash tier caches are available in the
 
 #### Availability zone redeployment and migration
 
-Currently, the only way to convert your cache from a non-AZ configuration to an AZ configuration is to redeploy the cache. To learn how to redeploy your current cache, see [Migrate an Azure Cache for Redis instance to availability zone support](/azure/reliability/migrate-cache-redis).
-
-> [!NOTE]
-   > Converting an existing resource from non-availability zone support to availability zone support is in Preview for Standard and Premium tier caches.
+In the Standard and Premium tiers, you can upgrade an existing resource to use zone redundancy. To learn how to upgrade your current cache, see [Migrate an Azure Cache for Redis instance to availability zone support](/azure/reliability/migrate-cache-redis).
 
 ## Persistence
 

articles/azure-cache-for-redis/cache-how-to-zone-redundancy.md

@@ -16,7 +16,7 @@ In this article, you learn how to configure a zone-redundant Azure Cache instanc
 > [!NOTE]
    > In regions that don't support zones, the option to enable zone redundancy is disabled. For a list of regions that support zones, see [Azure Cache for Redis - zones supported regions](cache-high-availability.md#regional-availability).
 
-Azure Cache for Redis Standard (preview), Premium, and Enterprise tiers provide built-in redundancy by hosting each cache on two dedicated virtual machines (VMs). Even though these VMs are located in separate [Azure fault and update domains](/azure/virtual-machines/availability) and highly available, they're susceptible to data center-level failures. Azure Cache for Redis also supports zone redundancy in its Standard (preview), Premium, and Enterprise tiers. A zone-redundant cache runs on VMs spread across multiple [Availability Zones](../reliability/availability-zones-overview.md). It provides higher resilience and availability.
+Azure Cache for Redis Standard, Premium, and Enterprise tiers provide built-in redundancy by hosting each cache on two dedicated virtual machines (VMs). Even though these VMs are located in separate [Azure fault and update domains](/azure/virtual-machines/availability) and highly available, they're susceptible to data center-level failures. Azure Cache for Redis also supports zone redundancy in its Standard, Premium, and Enterprise tiers. A zone-redundant cache runs on VMs spread across multiple [Availability Zones](../reliability/availability-zones-overview.md). It provides higher resilience and availability.
 
 ## Prerequisites
 
@@ -132,7 +132,7 @@ A Premium cache has one primary and one replica node by default. To configure zo
 
 ### Can I update my existing Standard or Premium cache to use zone redundancy?
 
-- Yes, updating an existing Standard or Premium cache to use zone redundancy is supported in-place (Preview). Users can enable it by navigating to the **Advanced settings** on the Resource menu and selecting **Allocate Zones automatically** check-box followed by the save button. You can't disable zone redundancy once you enable it.
+- Yes, updating an existing Standard or Premium cache to use zone redundancy is supported in-place. Users can enable it by navigating to the **Advanced settings** on the Resource menu and selecting **Allocate Zones automatically** check-box followed by the save button. You can't disable zone redundancy once you enable it.
 - For more details, look into [Migrate an Azure Cache for Redis instance to availability zone support](/azure/reliability/migrate-cache-redis)
 - This can also be done by passing `ZonalAllocationPolicy` as `Automatic`in the request body while updating the cache. For more information regarding the update process using REST API, see [Update - ZonalAllocationPolicy](/rest/api/redis/redis/update#zonalallocationpolicy).
   - Updating `ZonalAllocationPolicy` to any other value than `Automatic`isn't supported.