Merge pull request MicrosoftDocs#16310 from exchange12rocks/master

GitHubber17 · web-flow · commit dd117886ef2e · 2018-10-05T15:54:02.000-07:00
Corrects a typo: sever -&gt; server
diff --git a/articles/biztalk-services/biztalk-migrating-to-edi-guide.md b/articles/biztalk-services/biztalk-migrating-to-edi-guide.md
@@ -23,7 +23,7 @@ Reviewers: Karthik Bharthy
 Written using:  Microsoft Azure BizTalk Services – February 2014 release.
 
 ## Introduction
-Electronic Data Interchange (EDI) is one of the most prevalent means by which businesses exchange data electronically, also termed as Business-to-Business or B2B transactions. BizTalk Server has had EDI support for over a decade since the initial BizTalk Sever release. With BizTalk Services, Microsoft continues the support for EDI solutions on the Microsoft Azure platform. B2B transactions are mostly external to an organization, and hence it’s easier to implement if it was implemented on a cloud platform. Microsoft Azure provides this capability through BizTalk Services.
+Electronic Data Interchange (EDI) is one of the most prevalent means by which businesses exchange data electronically, also termed as Business-to-Business or B2B transactions. BizTalk Server has had EDI support for over a decade since the initial BizTalk Server release. With BizTalk Services, Microsoft continues the support for EDI solutions on the Microsoft Azure platform. B2B transactions are mostly external to an organization, and hence it’s easier to implement if it was implemented on a cloud platform. Microsoft Azure provides this capability through BizTalk Services.
 
 While some customers look at BizTalk Services as a "green field" platform for new EDI solutions, many customers have current BizTalk Server EDI solutions that they may want to migrate to Azure. Because BizTalk Services EDI is architected based on the same key entities as BizTalk Server EDI architecture (trading partners, entities, agreements), it is possible to migrate BizTalk Server EDI artifacts to BizTalk Services.
 
diff --git a/articles/machine-learning/desktop-workbench/data-prep-appendix2-supported-data-sources.md b/articles/machine-learning/desktop-workbench/data-prep-appendix2-supported-data-sources.md
@@ -111,7 +111,7 @@ Scale-out execution relies on Spark's Parquet reading capabilities and supports
 A local hard drive or a mapped network storage location.
 
 ### SQL Server
-On-prem SQL sever, or Azure SQL database.
+On-prem SQL server, or Azure SQL database.
 
 ### Azure Blob storage
 Azure Blob storage, which requires an Azure subscription.
diff --git a/articles/security/azure-database-security-checklist.md b/articles/security/azure-database-security-checklist.md
@@ -59,7 +59,7 @@ Azure Database is a robust database platform, with a full range of security feat
 ## Next steps
 You can improve the protection of your database against malicious users or unauthorized access with just a few simple steps. In this tutorial you learn to:
 
-- Set up [firewall rules](https://docs.microsoft.com/azure/sql-database/sql-database-firewall-configure) for your sever and or database.
+- Set up [firewall rules](https://docs.microsoft.com/azure/sql-database/sql-database-firewall-configure) for your server and or database.
 - Protect your data with [encryption](https://docs.microsoft.com/sql/relational-databases/security/encryption/sql-server-encryption).
 - Enable [SQL Database auditing](https://docs.microsoft.com/azure/sql-database/sql-database-auditing).
 
diff --git a/articles/sql-database/sql-database-security-tutorial.md b/articles/sql-database/sql-database-security-tutorial.md
@@ -168,7 +168,7 @@ Azure SQL Database Auditing tracks database events and writes them to an audit l
 
 1. Select **SQL databases** from the left-hand menu, and click your database on the **SQL databases** page. 
 
-2. In the Settings blade, select **Auditing & Threat Detection**. Notice that sever-level auditing is diabled and that there is a **View server settings** link that allows you to view or modify the server auditing settings from this context.
+2. In the Settings blade, select **Auditing & Threat Detection**. Notice that server-level auditing is disabled and that there is a **View server settings** link that allows you to view or modify the server auditing settings from this context.
 
     ![Auditing Blade](./media/sql-database-security-tutorial/auditing-get-started-settings.png)
 
diff --git a/articles/storage/files/storage-sync-files-troubleshoot.md b/articles/storage/files/storage-sync-files-troubleshoot.md
@@ -775,11 +775,11 @@ To monitor tiering activity on a server, use Event ID 9002, 9003, 9016 and 9029
 <a id="monitor-recall-activity"></a>**How to monitor recall activity on a server**  
 To monitor recall activity on a server, use Event ID 9005, 9006, 9007 in the Telemetry event log (located under Applications and Services\Microsoft\FileSync\Agent in Event Viewer). Note, these events are logged hourly.
 
-- Event ID 9005 provides recall reliability for a sever endpoint. For example, Total unique files accessed, Total unique files with failed access, etc.
+- Event ID 9005 provides recall reliability for a server endpoint. For example, Total unique files accessed, Total unique files with failed access, etc.
 
 - Event ID 9006 provides recall error distribution for a server endpoint. For example, Total Failed Requests, ErrorCode, etc. Note, one event is logged per error code.
 
-- Event ID 9007 provides recall performance for a sever endpoint. For example, TotalRecallIOSize, TotalRecallTimeTaken, etc.
+- Event ID 9007 provides recall performance for a server endpoint. For example, TotalRecallIOSize, TotalRecallTimeTaken, etc.
 
 <a id="files-fail-tiering"></a>**Troubleshoot files that fail to tier**  
 If files fail to tier to Azure Files:
diff --git a/includes/site-recovery-vmware-register-process-server.md b/includes/site-recovery-vmware-register-process-server.md
@@ -1,5 +1,5 @@
 * Connect to the Process Server virtual machine using Remote Desktop Connection.
-* You can launch the cspsconfigtool.exe by clicking on the shortcut available on the desktop. (The tool will be automatically launched if this the first time you are logging into the process sever).
+* You can launch the cspsconfigtool.exe by clicking on the shortcut available on the desktop. (The tool will be automatically launched if this the first time you are logging into the process server).
   - Configuration Server's fully qualified name (FQDN) or IP Address
   - Port on which the Configuration server is listening on. The value should be 443
   - Connection Passphrase to connect to the configuration server.
