vuild

Author: gitName

articles/api-management/TOC.yml

@@ -92,7 +92,7 @@
       - name: Migrate a VNet-injected instance
         href: migrate-stv1-to-stv2-vnet.md
     - name: Configure update settings
-      href: configure-update-settings.md
+      href: configure-service-update-settings.md
     - name: Move instances between regions
       href: api-management-howto-migrate.md
     - name: Recover a deleted instance

articles/api-management/configure-service-update-settings.md

@@ -64,7 +64,7 @@ Here's how to know about service updates that are expected or are in progress.
 
 ## Canary deployment strategies
 
-You can use an API Management instances assigned to a specific update group or deployed in a specific Azure region as a canary deployment that receives updates earlier than your production instances.
+You can use an API Management instance assigned to a specific update group or deployed in a specific Azure region as a canary deployment that receives updates earlier than your production instances.
 
 * **Add instance to Early update group** - Use an API Management instance in the Early update group to validate updates early in a production rollout. This instance is effectively your canary deployment.