Merge pull request #213898 from mikhailalmeida/release-arc-data

Updating docs for better readability.

Author: Stacyrch140

articles/azure-arc/data/includes/upgrade-rollback.md

@@ -2,35 +2,33 @@
 author: grrlgeek
 ms.service: azure-arc
 ms.topic: include
-ms.date: 07/07/2022
+ms.date: 10/22/2022
 ms.author: jeschult
 ---
 
-## Rollback 
+## Troubleshooting
 
-When you set the desired version, which can be done through Kubernetes, CLI, the portal, or Azure Data Studio, the bootstrap job will attempt to upgrade to that version until it succeeds. If the upgrade is successful, the `RunningVersion` property of the spec is updated to the new version. If the upgrade has a failure, there are several steps to troubleshoot. Common problems are an incorrect image tag, being unable to connect to the registry or repository, not enough CPU or memory in the containers, and not enough available storage.
+When the desired version is set to a specific version, the bootstrapper job will attempt to upgrade to that version until it succeeds. If the upgrade is successful, the `RunningVersion` property of the spec is updated to the new version. Upgrades could fail for scenarios such as an incorrect image tag, unable to connect to registry or repository, insufficient CPU or memory allocated to the containers,  or insufficient storage.
 
-1. To see which pod has an error or recent retarts, run 
+1. Run the below command to see if any of the pods show an `Error` status or have high number of restarts:
 
    ```console
-   kubectl get pods -n <namespace>
+   kubectl get pods --namespace <namespace>
    ```
 1. To look at Events to see if there is an error, run 
 
    ```console
-   kubectl describe pod <pod name> -n <namespace>
+   kubectl describe pod <pod name> --namespace <namespace>
    ```
 1. To get a list of the containers in the pods, run 
 
    ```console 
-   kubectl get pods <pod name> -n <namespace> -o jsonpath='{.spec.containers[*].name}*'
+   kubectl get pods <pod name> --namespace <namespace> -o jsonpath='{.spec.containers[*].name}*'
    ```
 1. To get the logs for a container, run  
 
    ```console
-   kubectl logs <pod name> <container name> -n <namespace>
+   kubectl logs <pod name> <container name> --namespace <namespace>
    ```
 
-## Troubleshooting
-
 To view common errors and how to troubleshoot them go to [Troubleshooting resources](..\troubleshoot-guide.md). 

articles/azure-arc/data/upgrade-active-directory-connector.md

@@ -11,22 +11,22 @@ ms.date: 10/11/2022
 ms.topic: how-to
 ---
 
-# Upgrade Active Directory connector (adc) for Azure SQL Managed Instance direct or indirect mode connected to Azure Arc
+# Upgrade Active Directory connector
 
-This article describes how to upgrade the Active Directory connector deployed on direct or indirect mode connected to Azure Arc-enabled data controller.
+This article describes how to upgrade the Active Directory connector.
 
 ## Prerequisites
 
 Before you can proceed with the tasks in this article, you need:
 
 - To connect and authenticate to a Kubernetes cluster
 - An existing Kubernetes context selected
-
-You need a direct or indirect mode connected to data controller with the `imageTag v1.2.0_2021-12-15` or greater.
+- Azure Arc data controller deployed, either in `direct` or `indirect` mode
+- Active Directory connector deployed
 
 ### Install tools
 
-To upgrade the active directory connector (adc), you need to have the Kubernetes tools installed.
+To upgrade the Active Directory connector (adc), you need to have the Kubernetes tools such as kubectl installed.
 
 The examples in this article use `kubectl`, but similar approaches could be used with other Kubernetes tools such as the Kubernetes dashboard, `oc`, or helm if you're familiar with those tools and Kubernetes yaml/json.
 
@@ -35,20 +35,15 @@ The examples in this article use `kubectl`, but similar approaches could be used
 
 ## Limitations
 
-The Azure Arc Data Controller must be upgraded to the new version before the active directory connector (adc) can be upgraded.
+Auto upgrade of Active Directory connector is applicable from imageTag `v1.12.0_2022-10-11` and above and the Arc data controller must be at least `v1.11.0_2022-09-13` version.
 
 The active directory connector (adc) must be at the same version as the data controller before a data controller is upgraded.
 
 There is no batch upgrade process available at this time.
 
-## Upgrade the active directory connector (adc)
-
-
-### Upgrade to `imageTag v1.12.0_2022-10-11` or greater
+## Upgrade Active Directory connector for previous versions
 
-The active directory connector (adc) automatically upgrades to the new version part of the data controller upgrade.
-
-### Upgrade prior to `imageTag v1.12.0_2022-10-11` or lower
+For imageTag versions `v1.11.0_2022-09-13` or lower, the Active Directory connector must be upgraded manually as below:
 
 Use a kubectl command to view the existing spec in yaml.
 
@@ -64,9 +59,7 @@ kubectl patch adc <adc-name> --namespace <namespace> --type merge --patch '{"spe
 
 ## Monitor
 
-You can monitor the progress of the upgrade with kubectl.
-
-### kubectl
+You can monitor the progress of the upgrade with kubectl as follows:
 
 ```console
 kubectl describe adc <adc-name> --namespace <namespace>

articles/azure-arc/data/upgrade-sql-managed-instance-indirect-kubernetes-tools.md

@@ -58,9 +58,7 @@ kubectl patch sqlmi <sqlmi-name> --namespace <namespace> --type merge --patch '{
 
 ## Monitor
 
-You can monitor the progress of the upgrade with kubectl.
-
-### kubectl
+You can monitor the progress of the upgrade with kubectl as follows:
 
 ```console
 kubectl describe sqlmi --namespace <namespace>