[SCOPED] Fix period before "and"

rwestMSFT · rwestMSFT · commit fe0ad30d111f · 2023-08-22T17:31:21.000-06:00
diff --git a/azure-sql/virtual-machines/windows/failover-cluster-instance-premium-file-share-manually-configure.md b/azure-sql/virtual-machines/windows/failover-cluster-instance-premium-file-share-manually-configure.md
@@ -42,7 +42,7 @@ Before you complete the instructions in this article, you should already have:
 
 To mount your premium file share, follow these steps: 
 
-1. Sign in to the [Azure portal](https://portal.azure.com). and go to your storage account.
+1. Sign in to the [Azure portal](https://portal.azure.com), and go to your storage account.
 1. Go to **File shares** under **Data storage**, and then select the premium file share you want to use for your SQL storage.
 1. Select **Connect** to bring up the connection string for your file share.
 1. In the drop-down list, select the drive letter you want to use, choose **Storage account key** as the authentication method, and then copy the code block to a text editor, such as Notepad.
diff --git a/docs/azure-data-studio/quickstart-azure-cosmos-db-mongodb.md b/docs/azure-data-studio/quickstart-azure-cosmos-db-mongodb.md
@@ -60,7 +60,7 @@ Your server will open in the **SERVERS** sidebar after you've successfully conne
 ### [API for MongoDB (vCore)](#tab/mongodb-vcore)
 
 1. Open the new Azure Cosmos DB for MongoDB (vCore) account in the Azure Portal.
-2. Navigate to "Settings" > "Connection string". and copy the shown "Connection string".
+2. Navigate to "Settings" > "Connection string", and copy the shown "Connection string".
 
     :::image type="content" source="media/quickstart-azure-cosmos-db-mongodb/connection-string-in-portal.png" lightbox="media/quickstart-azure-cosmos-db-mongodb/connection-string-in-portal.png" alt-text="Screenshot of the connection string in the portal.":::
 
diff --git a/docs/connect/jdbc/using-bulk-copy-with-the-jdbc-driver.md b/docs/connect/jdbc/using-bulk-copy-with-the-jdbc-driver.md
@@ -600,7 +600,7 @@ public class BulkCopyExistingTransactions {
   
 5. Select **Write a query to specify the data to transfer** and **Next**.  Enter your **SQL Statement** `SELECT ProductID, Name, ProductNumber FROM Production.Product`, and **Next**  
   
-6. Check the configuration: You can leave the Row delimiter as `{CR}{LF}` and Column Delimiter as Comma `{,}`.  Select **Edit Mappings**... and check that the data **Type** is correct for each column (for example, integer for `ProductID` and Unicode string for the others).  
+6. Check the configuration: You can leave the Row delimiter as `{CR}{LF}` and Column Delimiter as Comma `{,}`.  Select **Edit Mappings...** and check that the data **Type** is correct for each column (for example, integer for `ProductID` and Unicode string for the others).  
   
 7. Skip ahead to **Finish** and run the export.  
 
diff --git a/docs/integration-services/building-packages-programmatically/adding-connections-programmatically.md b/docs/integration-services/building-packages-programmatically/adding-connections-programmatically.md
@@ -40,7 +40,7 @@ The <xref:Microsoft.SqlServer.Dts.Runtime.ConnectionManager> class exposes a set
 
 This casts the managed connection manager object to its underlying connection object. If you use C++, the **QueryInterface** method of the <xref:Microsoft.SqlServer.Dts.Runtime.ConnectionManager> object is called and the interface of the underlying connection object is requested.
 
-The following table lists the connection managers included with [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)]. and the string that is used in the `package.Connections.Add("xxx")` statement. For a list of all connection managers, see [Integration Services (SSIS) Connections](../../integration-services/connection-manager/integration-services-ssis-connections.md).
+The following table lists the connection managers included with [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)], and the string that is used in the `package.Connections.Add("xxx")` statement. For a list of all connection managers, see [Integration Services (SSIS) Connections](../../integration-services/connection-manager/integration-services-ssis-connections.md).
 
 | String | Connection manager |
 | --- | --- |
diff --git a/docs/integration-services/service/package-management-ssis-service.md b/docs/integration-services/service/package-management-ssis-service.md
@@ -129,7 +129,7 @@ Stop a running package from the **Running Packages** folder by right-clicking th
   
 5.  Expand the subfolders to locate the folder into which you want to import a package.  
   
-6.  Right-click the folder, click **Import Package**. and then do one of the following:  
+6.  Right-click the folder, click **Import Package**, and then do one of the following:  
   
     -   To import from an instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], select the **SQL Server** option, and then specify the server and select the authentication mode. If you select [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Authentication, provide a user name and a password.  
   
diff --git a/docs/reporting-services/security/role-definitions-predefined-roles.md b/docs/reporting-services/security/role-definitions-predefined-roles.md
@@ -167,7 +167,7 @@ helpviewer_keywords:
 |Manage individual subscriptions|Create, view, modify, and delete subscriptions for reports and linked reports.|  
 |Manage report history|Create, view, and delete report history, view report history properties, and view, and modify settings that determine snapshot history limits and how caching works.|  
 |Manage reports|Add and delete reports, modify report parameters, view, and modify report properties, view and modify data sources that provide content to the report, view and modify report definitions, and set security policies at the report level.|  
-|Manage resources|Create, modify, and delete resources, and view. and modify resource properties.|  
+|Manage resources|Create, modify, and delete resources, and view and modify resource properties.|  
 |View data sources|View shared data source items in the folder hierarchy.|  
 |View folders|View folder contents.|  
 |View reports|Run reports that are stored in the user's My Reports folder and view report properties.|  
diff --git a/docs/t-sql/statements/create-materialized-view-as-select-transact-sql.md b/docs/t-sql/statements/create-materialized-view-as-select-transact-sql.md
@@ -150,7 +150,7 @@ A materialized view can be dropped via DROP VIEW.  You can use ALTER MATERIALIZE
 
 Materialized view is an automatic query optimization mechanism.  Users don't need to query a materialized view directly.  When a user query is submitted, the engine checks the user's permissions to the query objects and fails the query without execution if the user doesn't have access to the tables or regular views in the query.  If the user's permission has been verified, the optimizer automatically uses a matching materialized view to execute the query for faster performance.  Users get the same data back regardless if the query is served by querying the base tables or the materialized view.  
 
-EXPLAIN plan and the graphical Estimated Execution Plan in SQL Server Management Studio can show whether a materialized view is considered by the query optimizer for query execution. and the graphical Estimated Execution Plan in SQL Server Management Studio can show whether a materialized view is considered by the query optimizer for query execution.
+EXPLAIN plan and the graphical Estimated Execution Plan in SQL Server Management Studio can show whether a materialized view is considered by the query optimizer for query execution, and the graphical Estimated Execution Plan in SQL Server Management Studio can show whether a materialized view is considered by the query optimizer for query execution.
 
 To find out if a SQL statement can benefit from a new materialized view, run the `EXPLAIN` command with `WITH_RECOMMENDATIONS`.  For details, see [EXPLAIN (Transact-SQL)](../queries/explain-transact-sql.md?view=azure-sqldw-latest&preserve-view=true).
 
