Fixed bloking issues

Author: vladvino

articles/api-management/api-management-howto-configure-custom-domain-gateway.md

@@ -39,7 +39,7 @@ To perform the steps described in this article, you must have:
 
 1. Select **Certificates** from under **Security**.
 2. Select **+ Add**.
-3. Enter a resource name for the certificate into **Id** field.
+3. Enter a resource name for the certificate into **ID** field.
 4. Select the file containing the certificate (.PFX) by selecting the **Certificate** field or the folder icon adjacent to it.
 5. Enter the password for the certificate into the **Password** field.
 6. Select **Create** to add the certificate to your API Management service.

articles/api-management/how-to-deploy-self-hosted-gateway-docker.md

@@ -52,7 +52,7 @@ CONTAINER ID        IMAGE                                                 COMMAN
 ```
 10. Go back to Azure portal, click on **Overview** and confirm that self-hosted gateway container you just deployed is reporting a healthy status.
 
-![gateway status](media/api-management-howto-deploy-self-hosted-gateway-to-docker/status.png)
+![gateway status](media/how-to-deploy-self-hosted-gateway-docker/status.png)
 
 > [!TIP]
 > Use <code>console docker container logs <gateway-name></code> command to view a snapshot of self-hosted gateway log.

articles/api-management/how-to-deploy-self-hosted-gateway-kubernetes.md

@@ -48,7 +48,7 @@ NAME             TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)
 12. Go back to the Azure portal and select **Overview**.
 13. **Status** showing a green checkmark icon followed by the node count matching the number of replicas specified in the YAML file confirms that deployed self-hosted gateway pods are successfully communicating with the API Management service and have a regular "heartbeat".
 
-![gateway status](media/api-management-howto-deploy-self-hosted-gateway-to-k8s/status.png)
+![gateway status](media/how-to-deploy-self-hosted-gateway-kubernetes/status.png)
 
 > [!TIP]
 > Execute <code>kubectl logs deployment/<gateway-name></code> command to view logs from a randomly selected pod if there are more than one.

articles/api-management/media/api-management-howto-deploy-self-hosted-gateway-to-docker/status.png renamed to articles/api-management/media/how-to-deploy-self-hosted-gateway-docker/status.png

@@ -33,7 +33,7 @@ By default, all these components are deployed in Azure, causing all API traffic
 
 ![API traffic flow without self-hosted gateways](media/self-hosted-gateway-overview/without-gateways.png)
 
-Deploying self-hosted gateways into the same environments where the backend API implementations are hosted allows API traffic to flow directly to the backend APIs, which improves latency, optimizes data transfer costs, and enables compliance while retaining the benefits of having a single point of management, observanility, and discovery of all APIs within the organization regardless of where their implementations are hosted.
+Deploying self-hosted gateways into the same environments where the backend API implementations are hosted allows API traffic to flow directly to the backend APIs, which improves latency, optimizes data transfer costs, and enables compliance while retaining the benefits of having a single point of management, observability, and discovery of all APIs within the organization regardless of where their implementations are hosted.
 
 ![API traffic flow with self-hosted gateways](media/self-hosted-gateway-overview/with-gateways.png)