minor fixes. done with editing

Author: greg-lindsay

articles/application-gateway/for-containers/alb-controller-helm-chart.md

@@ -61,7 +61,7 @@ tolerations:
   effect: "NoSchedule"
 ```
 
-If desired, you can specify the toleration inline via helm install command via the following example:
+If desired, you can specify the toleration inline via the helm install command using the following example:
 
 ```bash
 HELM_NAMESPACE='<namespace for deployment>'

articles/application-gateway/for-containers/quickstart-deploy-application-gateway-for-containers-alb-controller.md

@@ -125,7 +125,7 @@ You need to complete the following tasks before deploying Application Gateway fo
         --issuer "$AKS_OIDC_ISSUER" \
         --subject "system:serviceaccount:azure-alb-system:alb-controller-sa"
     ```
-    ALB Controller requires a federated credential with the name of _azure-alb-identity_. Any other federated credential name is unsupported.
+    ALB Controller requires a federated credential with the name of `azure-alb-identity`. Any other federated credential name is unsupported.
 
    > [!Note]
    > Assignment of the managed identity immediately after creation may result in an error that the principalId does not exist. Allow about a minute of time to elapse for the identity to replicate in Microsoft Entra ID before delegating the identity.
@@ -136,7 +136,7 @@ You need to complete the following tasks before deploying Application Gateway fo
     
     To install ALB Controller, use the `helm install` command.
 
-    When the `helm install` command is run, it deploys the helm chart to the  _default_ namespace. When alb-controller is deployed, it deploys to the _azure-alb-system_ namespace. Both of these namespaces may be overridden independently as desired. To override the namespace the helm chart is deployed to, you may specify the --namespace (or -n) parameter. To override the _azure-alb-system_ namespace used by alb-controller, you may set the albController.namespace property during installation (`--set albController.namespace`). If neither the `--namespace` or the `--set albController.namespace` parameters are defined, the _default_ namespace is used for the helm chart and the _azure-alb-system_ namespace is used for the ALB controller components. Lastly, if the namespace for the helm chart resource isn't yet defined, ensure the `--create-namespace` parameter is also specified along with the `--namespace` or `-n` parameters.
+    When the `helm install` command is run, it deploys the helm chart to the  _default_ namespace. When alb-controller is deployed, it deploys to the `azure-alb-system` namespace. Both of these namespaces may be overridden independently as desired. To override the namespace the helm chart is deployed to, you may specify the --namespace (or -n) parameter. To override the `azure-alb-system` namespace used by alb-controller, you may set the albController.namespace property during installation (`--set albController.namespace`). If neither the `--namespace` or the `--set albController.namespace` parameters are defined, the _default_ namespace is used for the helm chart and the `azure-alb-system` namespace is used for the ALB controller components. Lastly, if the namespace for the helm chart resource isn't yet defined, ensure the `--create-namespace` parameter is also specified along with the `--namespace` or `-n` parameters.
     
     ALB Controller can be installed by running the following commands:
 
@@ -220,27 +220,27 @@ The next step is to link your ALB controller to Application Gateway for Containe
 
 There are two deployment strategies for management of Application Gateway for Containers:
 - **Bring your own (BYO) deployment:** In this deployment strategy, deployment and lifecycle of the Application Gateway for Containers resource, Association resource, and Frontend resource is assumed via Azure portal, CLI, PowerShell, Terraform, etc. and referenced in configuration within Kubernetes.
-   - To use a BYO deployment, see [Create Application Gateway for Containers - bring your own deployment](quickstart-create-application-gateway-for-containers-byo-deployment.md)
+   - To use a BYO deployment, see [Create Application Gateway for Containers - bring your own deployment](quickstart-create-application-gateway-for-containers-byo-deployment.md).
 - **Managed by ALB controller:** In this deployment strategy, ALB Controller deployed in Kubernetes is responsible for the lifecycle of the Application Gateway for Containers resource and its sub resources. ALB Controller creates an Application Gateway for Containers resource when an **ApplicationLoadBalancer** custom resource is defined on the cluster. The service lifecycle is based on the lifecycle of the custom resource.
-  - To use an ALB managed deployment, see [Create Application Gateway for Containers managed by ALB Controller](quickstart-create-application-gateway-for-containers-managed-by-alb-controller.md)
+  - To use an ALB managed deployment, see [Create Application Gateway for Containers managed by ALB Controller](quickstart-create-application-gateway-for-containers-managed-by-alb-controller.md).
 
 ## Uninstall Application Gateway for Containers and ALB Controller
 
 If you wish to uninstall the ALB Controller, complete the following steps.
 
 1. Delete the Application Gateway for Containers, you can delete the Resource Group containing the Application Gateway for Containers resources:
 
-```azurecli-interactive
-az group delete --resource-group $RESOURCE_GROUP
-```
+ ```azurecli-interactive
+ az group delete --resource-group $RESOURCE_GROUP
+ ```
 
 2. Uninstall ALB Controller and its resources from your cluster run the following commands:
 
-```azurecli-interactive
-helm uninstall alb-controller
-kubectl delete ns azure-alb-system
-kubectl delete gatewayclass azure-alb-external
-```
+ ```azurecli-interactive
+ helm uninstall alb-controller
+ kubectl delete ns azure-alb-system
+ kubectl delete gatewayclass azure-alb-external
+ ```
 
 > [!Note]
 > If a different namespace was used for alb-controller installation, ensure you specify the -n parameter on the helm uninstall command to define the proper namespace to be used. For example: `helm uninstall alb-controller -n unique-namespace`