Merge pull request #21375 from MicrosoftDocs/FromPublicRepo

Confirm merge from FromPublicRepo to main to sync with https://github.com/MicrosoftDocs/sql-docs (branch live)

Author: huypub

docs/big-data-cluster/deploy-openshift.md

@@ -73,7 +73,7 @@ This article outlines deployment steps that are specific to the OpenShift platfo
 
    ```console
    oc create clusterrole bdc-role --verb=use --resource=scc --resource-name=bdc-scc -n <namespaceName>
-   oc create rolebinding bdc-rbac --clusterrole=bdc-role --group=system:serviceaccounts:mssql-bdc
+   oc create rolebinding bdc-rbac --clusterrole=bdc-role --group=system:serviceaccounts:<namespaceName>
    ```
 
 5. Assign appropriate permission to the user deploying BDC. Do one of the following. 

docs/relational-databases/tables/primary-and-foreign-key-constraints.md

@@ -38,7 +38,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
 
 -   The index generated by a primary key constraint cannot cause the number of indexes on the table to exceed 999 nonclustered indexes and 1 clustered index.  
 
--   If clustered or nonclustered is not specified for a primary key constraint, clustered is used if there no clustered index on the table.  
+-   If clustered or nonclustered is not specified for a primary key constraint, clustered is used if there is no clustered index on the table.  
 
 -   All columns defined within a primary key constraint must be defined as not null. If nullability is not specified, all columns participating in a primary key constraint have their nullability set to not null.