20210702 1812

WilliamDAssafMSFT · WilliamDAssafMSFT · commit c81c97b8bd6c · 2021-07-02T18:12:44.000-07:00
diff --git a/docs/big-data-cluster/deploy-on-aks.md b/docs/big-data-cluster/deploy-on-aks.md
@@ -2,11 +2,11 @@
 title: Configure Azure Kubernetes Service
 titleSuffix: SQL Server Big Data Clusters
 description: Learn how to configure Azure Kubernetes Service (AKS) for SQL Server 2019 big data cluster deployments.
-author: MikeRayMSFT
-ms.author: mikeray
-ms.reviewer: mihaelab
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.reviewer: 
 ms.metadata: seo-lt-2019
-ms.date: 12/13/2019
+ms.date: 07/02/2021
 ms.topic: conceptual
 ms.prod: sql
 ms.technology: big-data-cluster
@@ -98,7 +98,7 @@ Before you run the command, update the script. Replace `<Azure data center>` wit
    az aks get-versions `
    --location <Azure data center> `
    --query orchestrators `
-   --o table
+   -o table
    ```
 
 Choose the latest available version for your cluster. Record the version number. You will use it in the next step.
diff --git a/docs/big-data-cluster/deployment-custom-configuration.md b/docs/big-data-cluster/deployment-custom-configuration.md
@@ -2,8 +2,8 @@
 title: Configure deployments
 titleSuffix: SQL Server big data clusters
 description: Learn how to customize a big data cluster deployment with configuration files that are built into the azdata management tool.
-author: MikeRayMSFT 
-ms.author: mikeray
+author: WilliamDAssafMSFT
+ms.author: wiassaf
 ms.reviewer: rajmera3
 ms.date: 02/11/2021
 ms.topic: conceptual
@@ -12,7 +12,7 @@ ms.technology: big-data-cluster
 ---
 
 
-# Configure deployment settings for cluster resources and services
+# Configure deployment settings for Big Data Cluster resources and services
 
 [!INCLUDE[SQL Server 2019](../includes/applies-to-version/sqlserver2019.md)]
 > [!Note]
@@ -334,7 +334,7 @@ First create a patch.json file as below that adjust the *storage* settings
                                 }
                         }
                 },
-		{
+        {
                         "op": "add",
                         "path": "spec.resources.master.spec.storage",
                         "value": {
diff --git a/docs/big-data-cluster/deployment-guidance.md b/docs/big-data-cluster/deployment-guidance.md
@@ -2,9 +2,9 @@
 title: Deployment guidance
 titleSuffix: SQL Server Big Data Clusters
 description: Learn how to deploy SQL Server Big Data Clusters on Kubernetes.
-author: MikeRayMSFT 
-ms.author: mikeray
-ms.reviewer: mihaelab
+author: WilliamDAssafMSFT
+ms.author: wiassaf
+ms.reviewer: 
 ms.date: 06/22/2020
 ms.topic: conceptual
 ms.prod: sql
@@ -15,7 +15,7 @@ ms.technology: big-data-cluster
 
 [!INCLUDE[SQL Server 2019](../includes/applies-to-version/sqlserver2019.md)]
 
-A SQL Server big data cluster is deployed as docker containers on a Kubernetes cluster. This is an overview of the setup and configuration steps:
+SQL Server Big Data Cluster is deployed as docker containers on a Kubernetes cluster. This is an overview of the setup and configuration steps:
 
 - Set up a Kubernetes cluster on a single VM, cluster of VMs, in Azure Kubernetes Service (AKS), Red Hat OpenShift or in Azure Red Hat OpenShift (ARO).
 - Install the cluster configuration tool [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)] on your client machine.
@@ -25,7 +25,7 @@ A SQL Server big data cluster is deployed as docker containers on a Kubernetes c
 
 See [Supported platforms](release-notes-big-data-cluster.md#supported-platforms) for a complete list of the various Kubernetes platforms validated for deploying SQL Server Big Data Clusters.
 
-### SQL Server Editions
+### SQL Server editions
 
 |Edition|Notes|
 |---------|---------|
@@ -58,15 +58,16 @@ kubectl config view
 ```
 
 > [!Important] 
-> If you are deploying on a multi node Kuberntes cluster that you bootstrapped using `kubeadm`, before starting the big data cluster deployment, ensure the clocks are synchronized across all the Kubernetes nodes the deployment is targeting. The big data cluster has built-in health properties for various services that are time sensitive and clock skews can result in incorrect status.
+> If you are deploying on a multi node Kubernetes cluster that you bootstrapped using `kubeadm`, before starting the big data cluster deployment, ensure the clocks are synchronized across all the Kubernetes nodes the deployment is targeting. The big data cluster has built-in health properties for various services that are time sensitive and clock skews can result in incorrect status.
 
 After you have configured your Kubernetes cluster, you can proceed with the deployment of a new SQL Server big data cluster. If you are upgrading from a previous release, please see [How to upgrade [!INCLUDE[big-data-clusters-2019](../includes/ssbigdataclusters-ss-nover.md)]](deployment-upgrade.md).
 
 ## Ensure you have storage configured
 
-Most big data cluster deployments should have persistent storage. At this time, you need to make sure you have a plan for how you're going to provide persistent storage on the Kubernetes cluster before you deploy the BDC.
+Most big data cluster deployments should have persistent storage. At this time, you need to make sure you have a plan for how you're going to provide persistent storage on the Kubernetes cluster before you deploy.
 
-If you deploy in AKS, no storage setup is necessary. AKS provides built-in storage classes with dynamic provisioning. You can customize the storage class (`default` or `managed-premium`) in the deployment configuration file. The built-in profiles use a `default` storage class. If you are deploying on a Kubernetes cluster you deployed using `kubeadm`, you'll need to ensure you have sufficient storage for a cluster of your desired scale available and configured for use. If you wish to customize how your storage is used, you should do this before proceeding. See [Data persistence with SQL Server big data cluster on Kubernetes](concept-data-persistence.md).
+ - If you deploy in AKS, no storage setup is necessary. AKS provides built-in storage classes with dynamic provisioning. You can customize the storage class (`default` or `managed-premium`) in the deployment configuration file. The built-in profiles use a `default` storage class. 
+ - If you are deploying on a Kubernetes cluster you deployed using `kubeadm`, you'll need to ensure you have sufficient storage for a cluster of your desired scale available and configured for use. If you wish to customize how your storage is used, you should do this before proceeding. See [Data persistence with SQL Server big data cluster on Kubernetes](concept-data-persistence.md).
 
 ## Install SQL Server 2019 Big Data tools
 
@@ -92,24 +93,24 @@ Big data cluster deployment options are defined in JSON configuration files. You
 > [!NOTE]
 > The container images required for the big data cluster deployment are hosted on Microsoft Container Registry (`mcr.microsoft.com`), in the `mssql/bdc` repository. By default, these settings are already included in the `control.json` configuration file in each of the deployment profiles included with [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)]. In addition, the container image tag for each release is also pre-populated in the same configuration file. If you need to pull the container images into your own private container registry and or modify the container registry/repository settings, follow the instructions in the [Offline installation article](deploy-offline.md)
 
-Run this command to find what are the templates available:
+Run this command to find the templates available:
 
-```
+```bash
 azdata bdc config list -o table 
 ```
 
 The following templates are available as of SQL Server 2019 CU5: 
 
 | Deployment profile | Kubernetes environment |
 |---|---|
-| `aks-dev-test` | Deploy SQL Server big data cluster on Azure Kubernetes Service (AKS)|
-| `aks-dev-test-ha` | Deploy SQL Server big data cluster on Azure Kubernetes Service (AKS). Mission critical services like SQL Server master and HDFS name node are configured for high availability.|
-| `aro-dev-test`|Deploy SQL Server big data cluster on Azure Red Hat OpenShift for development and testing. <br/><br/>Introduced in SQL Server 2019 CU 5.|
-| `aro-dev-test-ha`|Deploy SQL Server big data cluster with high availability on a Red Hat OpenShift cluster for development and testing. <br/><br/>Introduced in SQL Server 2019 CU 5.|
-| `kubeadm-dev-test` | Deploy SQL Server big data cluster on a Kubernetes cluster created with kubeadm using a single or multiple physical or virtual machines.|
-| `kubeadm-prod`| Deploy SQL Server big data cluster on a Kubernetes cluster created with kubeadm using a single or multiple physical or virtual machines. Use this template to enable big data cluster services to integrate with Active Directory. Mission critical services like SQL Server master instance and HDFS name node are deployed in a highly available configuration.  |
-| `openshift-dev-test`|Deploy SQL Server big data cluster on a Red Hat OpenShift cluster for development and testing. <br/><br/>Introduced in SQL Server 2019 CU 5.|
-| `openshift-prod`|Deploy SQL Server big data cluster with high availability on a Red Hat OpenShift cluster. <br/><br/>Introduced in SQL Server 2019 CU 5.|
+| `aks-dev-test` | Deploy SQL Server Big Data Cluster on Azure Kubernetes Service (AKS)|
+| `aks-dev-test-ha` | Deploy SQL Server Big Data Cluster on Azure Kubernetes Service (AKS). Mission critical services like SQL Server master and HDFS name node are configured for high availability.|
+| `aro-dev-test`|Deploy SQL Server Big Data Cluster on Azure Red Hat OpenShift for development and testing. <br/><br/>Introduced in SQL Server 2019 CU 5.|
+| `aro-dev-test-ha`|Deploy SQL Server Big Data Cluster with high availability on a Red Hat OpenShift cluster for development and testing. <br/><br/>Introduced in SQL Server 2019 CU 5.|
+| `kubeadm-dev-test` | Deploy SQL Server Big Data Cluster on a Kubernetes cluster created with kubeadm using a single or multiple physical or virtual machines.|
+| `kubeadm-prod`| Deploy SQL Server Big Data Cluster on a Kubernetes cluster created with kubeadm using a single or multiple physical or virtual machines. Use this template to enable big data cluster services to integrate with Active Directory. Mission critical services like SQL Server master instance and HDFS name node are deployed in a highly available configuration.  |
+| `openshift-dev-test`|Deploy SQL Server Big Data Cluster on a Red Hat OpenShift cluster for development and testing. <br/><br/>Introduced in SQL Server 2019 CU 5.|
+| `openshift-prod`|Deploy SQL Server Big Data Cluster with high availability on a Red Hat OpenShift cluster. <br/><br/>Introduced in SQL Server 2019 CU 5.|
 
 You can deploy a big data cluster by running `azdata bdc create`. This prompts you to choose one of the default configurations and then guides you through the deployment.
 
@@ -150,27 +151,27 @@ It is also possible to customize your deployment to accommodate the workloads yo
    ```
 
    > [!TIP]
-   > You can also pass in the cluster name at deployment time using the *--name* parameter for *azdata create bdc* command. The parameters in the command have precedence over the values in the configuration files.
+   > You can also pass in the cluster name at deployment time using the *--name* parameter for `azdata create bdc` command. The parameters in the command have precedence over the values in the configuration files.
    >
    > A useful tool for finding JSON paths is the [JSONPath Online Evaluator](https://jsonpath.com/).
    >
-   In addition to passing key-value pairs, you can also provide inline JSON values or pass JSON patch files. For more information, see [Configure deployment settings for big data clusters](deployment-custom-configuration.md).
+   In addition to passing key-value pairs, you can also provide inline JSON values or pass JSON patch files. For more information, see [Configure deployment settings for Big Data Cluster resources and services](deployment-custom-configuration.md).
 
 1. Pass the custom configuration file to `azdata bdc create`. Note that you must set the required [environment variables](#env), otherwise the terminal prompts for the values:
 
    ```bash
    azdata bdc create --config-profile custom --accept-eula yes
    ```
 
-> For more information on the structure of a deployment configuration file, see the [Deployment configuration file reference](reference-deployment-config.md). For more configuration examples, see [Configure deployment settings for big data clusters](deployment-custom-configuration.md).
+> For more information on the structure of a deployment configuration file, see the [Deployment configuration file reference](reference-deployment-config.md). For more configuration examples, see [Configure deployment settings for Big Data Clusters](deployment-custom-configuration.md).
 
 ## <a id="env"></a> Environment variables
 
 The following environment variables are used for security settings that are not stored in a deployment configuration file. Note that Docker settings except credentials can be set in the configuration file.
 
 | Environment variable | Requirement |Description |
 |---|---|---|
-| `AZDATA_USERNAME` | Required |The username for SQL Server big data cluster administrator. A sysadmin login with the same name is created in SQL Server master instance. As a security best practice, `sa` account is disabled. <br/><br/>[!INCLUDE [big-data-cluster-root-user](../includes/big-data-cluster-root-user.md)]|
+| `AZDATA_USERNAME` | Required |The username for SQL Server Big Data Cluster administrator. A sysadmin login with the same name is created in SQL Server master instance. As a security best practice, `sa` account is disabled. <br/><br/>[!INCLUDE [big-data-cluster-root-user](../includes/big-data-cluster-root-user.md)]|
 | `AZDATA_PASSWORD` | Required |The password for the user accounts created above. On clusters deployed prior to SQL Server 2019 CU5, the same password is used for the `root` user, to secure Knox gateway and HDFS. |
 | `ACCEPT_EULA`| Required for first use of [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)]| Set to "yes". When set as an environment variable, it applies EULA to both SQL Server and [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)]. If not set as environment variable, you can include `--accept-eula=yes` in the first use of [!INCLUDE [azure-data-cli-azdata](../includes/azure-data-cli-azdata.md)] command.|
 | `DOCKER_USERNAME` | Optional | The username to access the container images in case they are stored in a private repository. See the [Offline deployments](deploy-offline.md) topic for more details on how to use a private Docker repository for big data cluster deployment.|
@@ -428,7 +429,7 @@ For more information on how to connect to the big data cluster, see [Connect to
 
 ## Next steps
 
-To learn more about big data cluster deployment, see the following resources:
+To learn more about SQL Server Big Data Cluster deployment, see the following resources:
 
 - [Configure deployment settings for big data clusters](deployment-custom-configuration.md)
 - [Perform an offline deployment of a SQL Server big data cluster](deploy-offline.md)
