[SCOPED] Replace "reboot" with "restart"

Author: rwestMSFT

azure-sql/managed-instance/winauth-azuread-troubleshoot.md

@@ -39,7 +39,7 @@ The following are some well-known error codes:
   1. Run `netsh winhttp reset autoproxy`
   2. Run `netsh winhttp reset proxy`
   3. In the Windows registry, find `Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\iphlpsvc\Parameters\ProxyMgr` and delete any subentry that has a configuration with a port `:8888`
-  4. Reboot the machine and try again using Windows Authentication
+  4. Restart the machine and try again using Windows Authentication
 
 - **0x52f** - Indicates that a referenced user name and authentication information are valid, but some user account restriction has prevented successful authentication. This can happen if you have an Azure AD conditional access policy configured. To mitigate the issue, you must exclude the Azure SQL Managed Instance Service Principal (named `<instance name> principal`) application in the CA rules.
 

azure-sql/migration-guides/virtual-machines/sql-server-failover-cluster-instance-to-sql-on-azure-vm.md

@@ -165,7 +165,7 @@ To prepare source machines, you'll need information from the cluster.
 >  
 > - Maintain disk ownership throughout the replication process until the final cutover. If there is a change in disk ownership, there is a chance that the volumes could be corrupted and replication would need to be to retriggered. Set the preferred owner for each disk to avoid transfer of ownership during the replication process.
 >  
-> - Avoid patching activities and system reboots during the replication process to avoid transfer of disk ownership.
+> - Avoid patching activities and system restarts during the replication process to avoid transfer of disk ownership.
 
 To prepare source machines, do the following:
 

azure-sql/virtual-machines/linux/rhel-high-availability-stonith-tutorial.md

@@ -336,7 +336,7 @@ In this section, we will enable and start the pcsd service, and then configure t
 
 ### Enable and start pcsd service and Pacemaker
 
-1. Run the commands on all nodes. These commands allow the nodes to rejoin the cluster after reboot.
+1. Run the commands on all nodes. These commands allow the nodes to rejoin the cluster after each node restarts.
 
     ```bash
     sudo systemctl enable pcsd

azure-sql/virtual-machines/windows/availability-group-clusterless-workgroup-configure.md

@@ -58,7 +58,7 @@ To configure the DNS suffix, follow these steps:
 
    ![Screenshot shows where to see your Full computer name.](./media/availability-group-clusterless-workgroup-configure/3-confirm-full-computer-name.png)
 
-1. Reboot the server when you are prompted to do so. 
+1. Restart the server when you are prompted to do so. 
 1. Repeat these steps on any other nodes to be used for the availability group. 
 
 ## Edit a host file

azure-sql/virtual-machines/windows/availability-group-manually-configure-prerequisites-tutorial-multi-subnet.md

@@ -177,7 +177,7 @@ To configure **DC-VM-1** as the domain controller, follow these steps:
     | **Domain Controller Options** |**DSRM Password** = Contoso!0000<br/>**Confirm Password** = Contoso!0000 |
 
 1. Select **Next** to go through the other pages in the wizard. On the **Prerequisites Check** page, verify that you see the following message: **All prerequisite checks passed successfully**. You can review any applicable warning messages, but it's possible to continue with the installation.
-1. Select **Install**. The **DC-VM-1** virtual machine automatically reboots.
+1. Select **Install**. The **DC-VM-1** virtual machine automatically restarts.
 
 ### Identify DNS IP address
 
@@ -206,7 +206,7 @@ To configure your virtual network for DNS, follow these steps:
 
 ### Configure second domain controller
 
-After the primary domain controller reboots, you can optionally configure the second domain controller for the purpose of high availability. If you do not want to configure a second domain controller, skip this step. However, a second domain controller is recommended in production environments.
+After the primary domain controller restarts, you can optionally configure the second domain controller for the purpose of high availability. If you do not want to configure a second domain controller, skip this step. However, a second domain controller is recommended in production environments.
 
 Set the preferred DNS server address, join the domain, and then configure the secondary domain controller.
 

azure-sql/virtual-machines/windows/availability-group-manually-migrate-multi-subnet.md

@@ -71,7 +71,7 @@ To migrate your availability group to a multi-subnet configuration, follow these
 
 1. Add the Cluster IP and Listener IP to the [primary replica server](availability-group-manually-configure-prerequisites-tutorial-multi-subnet.md?#add-secondary-ips-to-sql-server-vms). Adding these IP addresses is an online operation.
 
-1. In the Azure portal, move the secondary server to the new subnet by going to the virtual machine > **Networking > Network Interface > IP Configurations**. Moving the server to a new subnet reboots the secondary replica server.
+1. In the Azure portal, move the secondary server to the new subnet by going to the virtual machine > **Networking > Network Interface > IP Configurations**. Moving the server to a new subnet restarts the secondary replica server.
 
 1. Add the Cluster IP and the Listener IP to the [secondary replica server](availability-group-manually-configure-prerequisites-tutorial-multi-subnet.md?#add-secondary-ips-to-sql-server-vms). Adding these IP addresses is an online operation.
 

azure-sql/virtual-machines/windows/storage-configuration.md

@@ -166,7 +166,7 @@ To change your caching policy in the Azure portal, follow these steps:
 
    ![Screenshot showing the disk caching policy configuration in the Azure portal.](./media/storage-configuration/azure-disk-config.png)
 
-1. After the change takes effect, reboot the SQL Server VM and start the SQL Server service.
+1. After the change takes effect, restart the SQL Server VM and start the SQL Server service.
 
 
 ## Enable Write Accelerator

docs/ado/guide/remote-data-service/configuring-rds-on-windows-2000.md

@@ -25,7 +25,7 @@ If you experience difficulties getting RDS to function correctly after you upgra
 
 5.  Using Internet Services Manager, locate the Default Web site and view the properties of the MSADC virtual root. Inspect the Directory Security/IP Address and Domain Name Restrictions. If the "Access is Denied" is checked then select "Granted".  
 
- Be sure to try rebooting the server if the changes to do not appear to solve the problem at first.  
+ Be sure to try restarting the server if the changes to do not appear to solve the problem at first.  
 
 > [!IMPORTANT]
 >  Beginning with Windows 8 and Windows Server 2012, RDS server components are no longer included in the Windows operating system (see Windows 8 and [Windows Server 2012 Compatibility Cookbook](https://www.microsoft.com/download/details.aspx?id=27416) for more detail). RDS client components will be removed in a future version of Windows. Avoid using this feature in new development work, and plan to modify applications that currently use this feature. Applications that use RDS should migrate to [WCF Data Service](/dotnet/framework/wcf/).Beginning with Windows 8 and Windows Server 2012, RDS server components are no longer included in the Windows operating system. Migrate applications that use RDS to [WCF Data Service](/dotnet/framework/wcf/).  

docs/analytics-platform-system/apply-analytics-platform-system-hotfixes.md

@@ -19,7 +19,7 @@ This article discusses how to apply hotfixes to the Analytics Platform System so
 > Do not attempt to apply a Analytics Platform System hotfix if your appliance or any appliance component is down or in a failed over state. In that case, contact support for assistance.  
   
 > [!WARNING]  
-> Do not apply a Analytics Platform System hotfix while the appliance is in use. Applying a hotfix can cause appliance nodes to reboot. The hotfix should be applied during a maintenance window when the appliance is not being used.  
+> Do not apply a Analytics Platform System hotfix while the appliance is in use. Applying a hotfix can cause appliance nodes to restart. The hotfix should be applied during a maintenance window when the appliance is not being used.  
   
 ### Prerequisites  
 To perform these steps, you will need:  

docs/analytics-platform-system/configure-tls12-aps.md

@@ -12,7 +12,7 @@ ms.topic: "conceptual"
 
 # Configure TLS 1.2 in APS
 
-To secure APS to only use TLS 1.2, you will have to explicitly disable other protocol on all physical and virtual hosts. Disabling protocols require registry setting changes. Registry changes require a reboot of the virtual and physical hosts.
+To secure APS to only use TLS 1.2, you will have to explicitly disable other protocol on all physical and virtual hosts. Disabling protocols require registry setting changes. Registry changes require a restart of the virtual and physical hosts.
 
 > [!WARNING]
 > This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly that can cause data loss and require reinstalling of the operating system. We highly recommend back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:<br>