acrolinx

Author: CarlRabeler

docs/big-data-cluster/reference-azdata.md

@@ -29,7 +29,7 @@ The following article provides reference for the `sql` commands in the `azdata`
 |[azdata extension](reference-azdata-extension.md) | Manage and update CLI extensions. |
 |[azdata notebook](reference-azdata-notebook.md) | Commands for viewing, running, and managing notebooks from a terminal. |
 ## azdata login
-When your cluster is deployed, it will list the controller endpoint during deployment, which you should use to login.  If you do not know the controller endpoint, you may login by having your cluster's kube config on your system in the default location of <user home>/.kube/config or use the KUBECONFIG env var, i.e. export KUBECONFIG=path/to/.kube/config.  When you login, this cluster's namespace will be set to your active context.
+When your cluster is deployed, it will list the controller endpoint during deployment, which you should use to log in.  If you do not know the controller endpoint, you may log in by having your cluster's kube config on your system in the default location of <user home>/.kube/config or use the KUBECONFIG env var, such as export KUBECONFIG=path/to/.kube/config.  When you log in, this cluster's namespace will be set to your active context.
 ```bash
 azdata login [--auth] 
              [--endpoint -e]  
@@ -55,11 +55,11 @@ Login using active directory with an explicit principal.
 ```bash
 azdata login --auth ad --principal johndoe@COSTOSO.COM --endpoint https://<ip or domain name>:30080
 ```
-Log in interactively. Cluster name will always be prompted for if not specified as an argument. If you have the AZDATA_USERNAME, AZDATA_PASSWORD, and ACCEPT_EULA env variables set on your system, these will not be prompted for. If you have the kube config on your system or are using the KUBECONFIG env var to specify the path to the config, the interactive experience will first try to use the config and then prompt you if the config fails.
+Log in interactively. Cluster name will always be prompted for if not specified as an argument. If you have the AZDATA_USERNAME, AZDATA_PASSWORD, and ACCEPT_EULA env variables set on your system, these values will not be prompted for. If you have the kube config on your system or are using the KUBECONFIG env var to specify the path to the config, the interactive experience will first try to use the config and then prompt you if the config fails.
 ```bash
 azdata login
 ```
-Log in (non-interactively). Log in with cluster name, controller user name, controller endpoint, and EULA acceptance set as arguments. The environment variable AZDATA_PASSWORD must be set.  If you do not want to specify the controller endpoint, please have the kube config on your machine in the default location of <user home>/.kube/config or use the KUBECONFIG env var, i.e. export KUBECONFIG=path/to/.kube/config.
+Log in (non-interactively). Log in with cluster name, controller user name, controller endpoint, and EULA acceptance set as arguments. The environment variable AZDATA_PASSWORD must be set.  If you do not want to specify the controller endpoint, have the kube config on your machine in the default location of <user home>/.kube/config or use the KUBECONFIG env var, such as export KUBECONFIG=path/to/.kube/config.
 ```bash
 azdata login --namespace ClusterName --username johndoe@contoso.com  --endpoint https://<ip or domain name>:30080 --accept-eula yes
 ```
@@ -71,7 +71,7 @@ azdata login -n ClusterName
 #### `--auth`
 The authentication strategy. Basic or Active Directory authentication. Default is "basic" authentication.
 #### `--endpoint -e`
-Cluster controller endpoint "https://host:port". If you do not want to use this arg, you may use the kube config on your machine. Please ensure the config is located at the default location of <user home>/.kube/config or use the KUBECONFIG env var.
+Cluster controller endpoint "https://host:port". If you do not want to use this arg, you may use the kube config on your machine. Ensure the config is located at the default location of <user home>/.kube/config or use the KUBECONFIG env var.
 #### `--accept-eula -a`
 Do you accept the license terms? [yes/no]. If you do not want to use this arg, you may set the environment variable ACCEPT_EULA to 'yes'. The license terms for this product can be viewed at https://aka.ms/eula-azdata-en.
 #### `--namespace -n`
@@ -88,7 +88,7 @@ Show this help message and exit.
 #### `--output -o`
 Output format.  Allowed values: json, jsonc, table, tsv.  Default: json.
 #### `--query -q`
-JMESPath query string. See [http://jmespath.org/](http://jmespath.org) for more information and examples.
+JMESPath query string. For more information, see [http://jmespath.org/](http://jmespath.org) for more information and examples.
 #### `--verbose`
 Increase logging verbosity. Use --debug for full debug logs.
 ## azdata logout
@@ -109,7 +109,7 @@ Show this help message and exit.
 #### `--output -o`
 Output format.  Allowed values: json, jsonc, table, tsv.  Default: json.
 #### `--query -q`
-JMESPath query string. See [http://jmespath.org/](http://jmespath.org) for more information and examples.
+JMESPath query string. For more information, see [http://jmespath.org/](http://jmespath.org) for more information and examples.
 #### `--verbose`
 Increase logging verbosity. Use --debug for full debug logs.
 

docs/ssma/access/connecting-to-azure-sql-db-accesstosql.md

@@ -50,7 +50,7 @@ When you define the connection properties, you also specify the database where o
 
 2.  In the connection dialog box, enter or select the server name of SQL Azure.  
 
-3.  Enter, select or **Browse** the Database name.  
+3.  Enter, select, or **Browse** the Database name.  
 
 4.  Enter or select **UserName**.  
 
@@ -63,7 +63,7 @@ When you define the connection properties, you also specify the database where o
 > [!IMPORTANT]  
 > SSMA for Access does not support connection to **master** database in SQL Azure.  
   
-If there are no databases in the SQL Azure account, you can create the very first database using **Create Azure Database** option that appears on the click of **Browse** button.  
+If there are no databases in the SQL Azure account, you can create the first database using **Create Azure Database** option that appears on the click of **Browse** button.  
 
 ## Synchronizing SQL Azure Metadata  
 Metadata about SQL Azure databases is not automatically updated. The metadata in SQL Azure Metadata Explorer is a snapshot of the metadata when you first connected to SQL Azure, or the last time that you manually updated metadata. You can manually update metadata for all databases, or for any single database or database object.  
@@ -83,7 +83,7 @@ If SQL Azure schemas change after you connect, you can refresh metadata from the
 
 **To refresh SQL Azure metadata**  
 
--   In SQL Azure Metadata Explorer, right click **Databases**, and then select **Refresh from Database**.  
+-   In SQL Azure Metadata Explorer, right-click **Databases**, and then select **Refresh from Database**.  
 
 ## Reconnecting to SQL Azure  
 Your connection to SQL Azure stays active until you close the project. When you reopen the project, you must reconnect to SQL Azure if you want an active connection to the server. You can work offline until you load database objects into SQL Azure and migrate data.