Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into product-page-edit

Author: asudbring

articles/aks/availability-zones.md

@@ -100,7 +100,7 @@ kubectl describe nodes | grep -e "Name:" -e "topology.kubernetes.io/zone"
 
 The following example output shows the three nodes distributed across the specified region and availability zones, such as *eastus2-1* for the first availability zone and *eastus2-2* for the second availability zone:
 
-```console
+```output
 Name:       aks-nodepool1-28993262-vmss000000
             topology.kubernetes.io/zone=eastus2-1
 Name:       aks-nodepool1-28993262-vmss000001
@@ -113,13 +113,13 @@ As you add more nodes to an agent pool, the Azure platform automatically distrib
 
 With Kubernetes versions 1.17.0 and later, AKS uses the newer label `topology.kubernetes.io/zone` and the deprecated `failure-domain.beta.kubernetes.io/zone`. You can get the same result from running the `kubelet describe nodes` command in the previous step, by running the following script:
 
- ```console
+ ```bash
 kubectl get nodes -o custom-columns=NAME:'{.metadata.name}',REGION:'{.metadata.labels.topology\.kubernetes\.io/region}',ZONE:'{metadata.labels.topology\.kubernetes\.io/zone}'
 ```
 
 The following example resembles the output with more verbose details:
 
-```console
+```output
 NAME                                REGION   ZONE
 aks-nodepool1-34917322-vmss000000   eastus   eastus-1
 aks-nodepool1-34917322-vmss000001   eastus   eastus-2
@@ -139,7 +139,7 @@ az aks scale \
 
 When the scale operation completes after a few minutes, run the command `kubectl describe nodes | grep -e "Name:" -e "topology.kubernetes.io/zone"` in a Bash shell. The following output resembles the results:
 
-```console
+```output
 Name:       aks-nodepool1-28993262-vmss000000
             topology.kubernetes.io/zone=eastus2-1
 Name:       aks-nodepool1-28993262-vmss000001
@@ -161,7 +161,7 @@ kubectl scale deployment nginx --replicas=3
 
 By viewing nodes where your pods are running, you see pods are running on the nodes corresponding to three different availability zones. For example, with the command `kubectl describe pod | grep -e "^Name:" -e "^Node:"` in a Bash shell, you see the following example output:
 
-```console
+```output
 Name:         nginx-6db489d4b7-ktdwg
 Node:         aks-nodepool1-28993262-vmss000000/10.240.0.4
 Name:         nginx-6db489d4b7-v7zvj

articles/aks/upgrade-windows-2019-2022.md

@@ -58,7 +58,7 @@ Once you update the nodeSelector on the YAML file, you should also update the co
 
 If you have an application deployed already, follow the recommended steps to deploy a new node pool with Windows Server 2022 nodes. Once deployed, your environment will show Windows Server 2019 and 2022 nodes, with the workloads running on the 2019 nodes:
 
-```console
+```bash
 kubectl get nodes -o wide
 ```
 This command shows all nodes on your AKS cluster with extra details on the output:
@@ -76,7 +76,7 @@ akswspool000002                     Ready    agent   5h37m   v1.23.8   10.240.0.
 
 With the Windows Server 2022 node pool deployed and the YAML file configured, you can now deploy the new version of the YAML:
 
-```console
+```bash
 kubectl apply -f <filename>
 ```
 
@@ -88,7 +88,7 @@ service/sample unchanged
 ```
 At this point, AKS starts the process of terminating the existing pods and deploying new pods to the Windows Server 2022 nodes. You can check the status of your deployment by running:
 
-```console
+```bash
 kubectl get pods -o wide
 ```
 This command returns the status of the pods on the default namespace. You might need to change the command above to list the pods on specific namespaces. 
@@ -104,4 +104,4 @@ sample-7794bfcc4c-sh78c   1/1     Running   0          2m49s   10.240.0.228   ak
 
 If you're using Group Managed Service Accounts (gMSA), update the Managed Identity configuration for the new node pool. gMSA uses a secret (user account and password) so the node on which the Windows pod is running can authenticate the container against Active Directory. To access that secret on Azure Key Vault, the node uses a Managed Identity that allows the node to access the resource. Since Managed Identities are configured per node pool, and the pod now resides on a new node pool, you need to update that configuration. Check out [Enable Group Managed Service Accounts (GMSA) for your Windows Server nodes on your Azure Kubernetes Service (AKS) cluster](./use-group-managed-service-accounts.md) for more information.
 
-The same principle applies to Managed Identities used for any other pod/node pool when accessing other Azure resources. Any access provided via Managed Identity needs to be updated to reflect the new node pool. To view update and sign-in activities, see [How to view Managed Identity activity](../active-directory/managed-identities-azure-resources/how-to-view-managed-identity-activity.md).
+The same principle applies to Managed Identities used for any other pod/node pool when accessing other Azure resources. Any access provided via Managed Identity needs to be updated to reflect the new node pool. To view update and sign-in activities, see [How to view Managed Identity activity](../active-directory/managed-identities-azure-resources/how-to-view-managed-identity-activity.md).

articles/aks/use-multiple-node-pools.md

@@ -130,7 +130,7 @@ The ARM64 processor provides low power compute for your Kubernetes workloads. To
 
 Use `az aks nodepool add` command to add an ARM64 node pool.
 
-```azurecli
+```azurecli-interactive
 az aks nodepool add \
     --resource-group myResourceGroup \
     --cluster-name myAKSCluster \
@@ -145,7 +145,7 @@ Mariner is an open-source Linux distribution available as an AKS container host.
 
 You can add a Mariner node pool into your existing cluster using the `az aks nodepool add` command and specifying `--os-sku mariner`.
 
-```azurecli
+```azurecli-interactive
 az aks nodepool add \
     --resource-group myResourceGroup \
     --cluster-name myAKSCluster \
@@ -166,7 +166,7 @@ Use the following instructions to migrate your Ubuntu nodes to Mariner nodes.
 3. [Drain the existing Ubuntu nodes][drain-nodes].
 4. Remove the existing Ubuntu nodes using the `az aks delete` command.
 
-```azurecli
+```azurecli-interactive
 az aks nodepool delete \
     --resource-group myResourceGroup \
     --cluster-name myAKSCluster \
@@ -317,7 +317,7 @@ az aks nodepool scale \
 
 List the status of your node pools again using the [`az aks node pool list`][az-aks-nodepool-list] command. The following example shows that *mynodepool* is in the *Scaling* state with a new count of *5* nodes:
 
-```azurecli
+```azurecli-interactive
 az aks nodepool list -g myResourceGroup --cluster-name myAKSCluster
 ```
 
@@ -369,7 +369,7 @@ az aks nodepool delete -g myResourceGroup --cluster-name myAKSCluster --name myn
 
 The following example output from the [`az aks node pool list`][az-aks-nodepool-list] command shows that *mynodepool* is in the *Deleting* state:
 
-```azurecli
+```azurecli-interactive
 az aks nodepool list -g myResourceGroup --cluster-name myAKSCluster
 ```
 
@@ -416,13 +416,13 @@ For more information on the capacity reservation groups, please refer to [Capaci
 
 To install the aks-preview extension, run the following command:
 
-```azurecli
+```azurecli-interactive
 az extension add --name aks-preview
 ```
 
 Run the following command to update to the latest version of the extension released:
 
-```azurecli
+```azurecli-interactive
 az extension update --name aks-preview
 ```
 
@@ -490,7 +490,7 @@ az aks nodepool add \
 
 The following example output from the [`az aks node pool list`][az-aks-nodepool-list] command shows that *gpunodepool* is *Creating* nodes with the specified *VmSize*:
 
-```azurecli
+```azurecli-interactive
 az aks nodepool list -g myResourceGroup --cluster-name myAKSCluster
 ```
 
@@ -548,7 +548,7 @@ az aks nodepool add \
 
 The following example output from the [`az aks nodepool list`][az-aks-nodepool-list] command shows that *taintnp* is *Creating* nodes with the specified *nodeTaints*:
 
-```azurecli
+```azurecli-interactive
 az aks nodepool list -g myResourceGroup --cluster-name myAKSCluster
 ```
 
@@ -608,13 +608,13 @@ spec:
 
 Schedule the pod using the `kubectl apply -f nginx-toleration.yaml` command:
 
-```console
+```bash
 kubectl apply -f nginx-toleration.yaml
 ```
 
 It takes a few seconds to schedule the pod and pull the NGINX image. Use the [kubectl describe pod][kubectl-describe] command to view the pod status. The following condensed example output shows the *sku=gpu:NoSchedule* toleration is applied. In the events section, the scheduler has assigned the pod to the *aks-taintnp-28993262-vmss000000* node:
 
-```console
+```bash
 kubectl describe pod mypod
 ```
 

articles/aks/use-wasi-node-pools.md

@@ -23,13 +23,13 @@ You must have the latest version of Azure CLI installed.
 
 To install the aks-preview extension, run the following command:
 
-```azurecli
+```azurecli-interactive
 az extension add --name aks-preview
 ```
 
 Run the following command to update to the latest version of the extension released:
 
-```azurecli
+```azurecli-interactive
 az extension update --name aks-preview
 ```
 
@@ -85,31 +85,36 @@ az aks nodepool show -g myResourceGroup --cluster-name myAKSCluster -n mywasipoo
 
 The following example output shows the *mywasipool* has the *workloadRuntime* type of *WasmWasi*.
 
+```azurecli-interactive
+az aks nodepool show -g myResourceGroup --cluster-name myAKSCluster -n mywasipool --query workloadRuntime
+```
 ```output
-$ az aks nodepool show -g myResourceGroup --cluster-name myAKSCluster -n mywasipool --query workloadRuntime
 "WasmWasi"
 ```
 
 Configure `kubectl` to connect to your Kubernetes cluster using the [az aks get-credentials][az-aks-get-credentials] command. The following command:  
 
-```azurecli
+```azurecli-interactive
 az aks get-credentials -n myakscluster -g myresourcegroup
 ```
 
 Use `kubectl get nodes` to display the nodes in your cluster.
 
+```bash
+kubectl get nodes -o wide
+```
 ```output
-$ kubectl get nodes -o wide
 NAME                                 STATUS   ROLES   AGE    VERSION    INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME
 aks-mywasipool-12456878-vmss000000   Ready    agent   123m   v1.23.12   <WASINODE_IP> <none>        Ubuntu 22.04.1 LTS   5.15.0-1020-azure   containerd://1.5.11+azure-2
 aks-nodepool1-12456878-vmss000000    Ready    agent   133m   v1.23.12   <NODE_IP>     <none>        Ubuntu 22.04.1 LTS   5.15.0-1020-azure   containerd://1.5.11+azure-2
 ```
 
 Use `kubectl describe node` to show the labels on a node in the WASI node pool. The following example shows the details of *aks-mywasipool-12456878-vmss000000*.
 
+```bash
+kubectl describe node aks-mywasipool-12456878-vmss000000
+```
 ```output
-$ kubectl describe node aks-mywasipool-12456878-vmss000000
-
 Name:               aks-mywasipool-12456878-vmss000000
 Roles:              agent
 Labels:             agentpool=mywasipool
@@ -143,7 +148,7 @@ scheduling:
 
 Use `kubectl` to create the `RuntimeClass` objects.
 
-```azurecli-interactive
+```bash
 kubectl apply -f wasm-runtimeclass.yaml
 ```
 
@@ -198,14 +203,16 @@ spec:
 
 Use `kubectl` to run your example deployment:
 
-```azurecli-interactive
+```bash
 kubectl apply -f slight.yaml
 ```
 
 Use `kubectl get svc` to get the external IP address of the service.
 
+```bash
+kubectl get svc
+```
 ```output
-$ kubectl get svc
 NAME          TYPE           CLUSTER-IP     EXTERNAL-IP    PORT(S)        AGE
 kubernetes    ClusterIP      10.0.0.1       <none>         443/TCP        10m
 wasm-slight   LoadBalancer   10.0.133.247   <EXTERNAL-IP>  80:30725/TCP   2m47s
@@ -214,7 +221,7 @@ wasm-slight   LoadBalancer   10.0.133.247   <EXTERNAL-IP>  80:30725/TCP   2m47s
 Access the example application at `http://EXTERNAL-IP/hello`. The following example uses `curl`.
 
 ```output
-$ curl http://EXTERNAL-IP/hello
+curl http://EXTERNAL-IP/hello
 hello
 ```
 
@@ -225,7 +232,7 @@ hello
 
 To remove the example deployment, use `kubectl delete`.
 
-```azurecli-interactive
+```bash
 kubectl delete -f slight.yaml
 ```
 

articles/azure-app-configuration/use-feature-flags-dotnet-core.md

@@ -26,7 +26,7 @@ The Feature Management libraries also manage feature flag lifecycles behind the
 
 The [Add feature flags to an ASP.NET Core app Quickstart](./quickstart-feature-flag-aspnet-core.md) shows a simple example of how to use feature flags in an ASP.NET Core application. This tutorial shows additional setup options and capabilities of the Feature Management libraries. You can use the sample app created in the quickstart to try out the sample code shown in this tutorial. 
 
-For the ASP.NET Core feature management API reference documentation, see [Microsoft.FeatureManagement Namespace](https://www.nuget.org/packages/Microsoft.FeatureManagement/).
+For the ASP.NET Core feature management API reference documentation, see [Microsoft.FeatureManagement Namespace](/dotnet/api/microsoft.featuremanagement).
 
 In this tutorial, you will learn how to:
 
@@ -40,7 +40,7 @@ To access the .NET Core feature manager, your app must have references to the `M
 
 The .NET Core feature manager is configured from the framework's native configuration system. As a result, you can define your application's feature flag settings by using any configuration source that .NET Core supports, including the local *appsettings.json* file or environment variables.
 
-By default, the feature manager retrieves feature flag configuration from the `"FeatureManagement"` section of the .NET Core configuration data. To use the default configuration location, call the AddFeatureManagement method of the **IServiceCollection** passed into the **ConfigureServices** method of the **Startup** class.
+By default, the feature manager retrieves feature flag configuration from the `"FeatureManagement"` section of the .NET Core configuration data. To use the default configuration location, call the [AddFeatureManagement](/dotnet/api/microsoft.featuremanagement.servicecollectionextensions.addfeaturemanagement) method of the **IServiceCollection** passed into the **ConfigureServices** method of the **Startup** class.
 
 
 ```csharp
@@ -72,7 +72,7 @@ public class Startup
 ```
 
 
-If you use filters in your feature flags, you must include the [Microsoft.FeatureManagement.FeatureFilters](/dotnet/api/microsoft.azure.management.storsimple8000series.models.featurefilter) namespace and add a call to AddFeatureFilters specifying the type name of the filter you want to use as the generic type of the method. For more information on using feature filters to dynamically enable and disable functionality, see [Enable staged rollout of features for targeted audiences](./howto-targetingfilter-aspnet-core.md).
+If you use filters in your feature flags, you must include the [Microsoft.FeatureManagement.FeatureFilters](/dotnet/api/microsoft.featuremanagement.featurefilters) namespace and add a call to [AddFeatureFilter](/dotnet/api/microsoft.featuremanagement.ifeaturemanagementbuilder.addfeaturefilter) specifying the type name of the filter you want to use as the generic type of the method. For more information on using feature filters to dynamically enable and disable functionality, see [Enable staged rollout of features for targeted audiences](./howto-targetingfilter-aspnet-core.md).
 
 The following example shows how to use a built-in feature filter called `PercentageFilter`:
 
@@ -217,7 +217,7 @@ By convention, the `FeatureManagement` section of this JSON document is used for
 
 ## Use dependency injection to access IFeatureManager 
 
-For some operations, such as manually checking feature flag values, you need to get an instance of IFeatureManager. In ASP.NET Core MVC, you can access the feature manager `IFeatureManager` through dependency injection. In the following example, an argument of type `IFeatureManager` is added to the signature of the constructor for a controller. The runtime automatically resolves the reference and provides an of the interface when calling the constructor. If you're using an application template in which the controller already has one or more dependency injection arguments in the constructor, such as `ILogger`, you can just add `IFeatureManager` as an additional argument:
+For some operations, such as manually checking feature flag values, you need to get an instance of [IFeatureManager](/dotnet/api/microsoft.featuremanagement.ifeaturemanager). In ASP.NET Core MVC, you can access the feature manager `IFeatureManager` through dependency injection. In the following example, an argument of type `IFeatureManager` is added to the signature of the constructor for a controller. The runtime automatically resolves the reference and provides an of the interface when calling the constructor. If you're using an application template in which the controller already has one or more dependency injection arguments in the constructor, such as `ILogger`, you can just add `IFeatureManager` as an additional argument:
 
 ### [.NET 5.x](#tab/core5x)
 
@@ -321,7 +321,7 @@ public IActionResult Index()
 }
 ```
 
-When an MVC controller or action is blocked because the controlling feature flag is *off*, a registered IDisabledFeaturesHandler interface is called. The default `IDisabledFeaturesHandler` interface returns a 404 status code to the client with no response body.
+When an MVC controller or action is blocked because the controlling feature flag is *off*, a registered [IDisabledFeaturesHandler](/dotnet/api/microsoft.featuremanagement.mvc.idisabledfeatureshandler) interface is called. The default `IDisabledFeaturesHandler` interface returns a 404 status code to the client with no response body.
 
 ## MVC views
 
@@ -396,5 +396,5 @@ app.UseForFeature(featureName, appBuilder => {
 In this tutorial, you learned how to implement feature flags in your ASP.NET Core application by using the `Microsoft.FeatureManagement` libraries. For more information about feature management support in ASP.NET Core and App Configuration, see the following resources:
 
 * [ASP.NET Core feature flag sample code](./quickstart-feature-flag-aspnet-core.md)
-* [Microsoft.FeatureManagement documentation](https://www.nuget.org/packages/Microsoft.FeatureManagement/)
+* [Microsoft.FeatureManagement documentation](/dotnet/api/microsoft.featuremanagement)
 * [Manage feature flags](./manage-feature-flags.md)

articles/cognitive-services/Translator/containers/translator-how-to-install-container.md

@@ -68,7 +68,7 @@ The following table describes the minimum and recommended CPU cores and memory t
 
 | Container | Minimum |Recommended | Language Pair |
 |-----------|---------|---------------|----------------------|
-| Translator connected |`2` cores, 2-GB memory |`4` cores, 8-GB memory | 4 |
+| Translator |`2` cores, 2-GB memory |`4` cores, 8-GB memory | 4 |
 
 * Each core must be at least 2.6 gigahertz (GHz) or faster. 
 
@@ -92,9 +92,9 @@ Application for Gated Services**](https://aka.ms/csgate-translator) to request a
 
 ## Translator container image
 
-The Translator container image can be found on the `mcr.microsoft.com` container registry syndicate. It resides within the `azure-cognitive-services/translator` repository and is named `text-translation`. The fully qualified container image name is `mcr.microsoft.com/azure-cognitive-services/translator/text-translation:1.0.019410001-amd64-preview`.
+The Translator container image can be found on the `mcr.microsoft.com` container registry syndicate. It resides within the `azure-cognitive-services/translator` repository and is named `text-translation`. The fully qualified container image name is `mcr.microsoft.com/azure-cognitive-services/translator/text-translation:latest`.
 
-To use the latest version of the container, you can use the `latest` tag. You can also find a full list of [tags on the MCR](https://mcr.microsoft.com/product/azure-cognitive-services/translator/text-translation/tags).
+To use the latest version of the container, you can use the `latest` tag. You can find a full list of [tags on the MCR](https://mcr.microsoft.com/product/azure-cognitive-services/translator/text-translation/tags).
 
 ## Get container images with **docker commands**
 
@@ -112,7 +112,7 @@ docker run --rm -it -p 5000:5000 --memory 12g --cpus 4 \
 -e eula=accept \
 -e billing={ENDPOINT_URI} \
 -e Languages=en,fr,es,ar,ru  \
-mcr.microsoft.com/azure-cognitive-services/translator/text-translation:1.0.019410001-amd64-preview
+mcr.microsoft.com/azure-cognitive-services/translator/text-translation:latest
 ```
 
 The above command: