update Asterisks to underscore

Saisang · Saisang · commit 8eab7fc9975e · 2019-08-30T11:28:50.000-07:00
diff --git a/docs/ado/guide/data/ado-event-instantiation-ado-and-wfc.md b/docs/ado/guide/data/ado-event-instantiation-ado-and-wfc.md
@@ -34,7 +34,7 @@ ADO for Windows Foundation Classes (ADO/WFC) builds on the ADO event model and p
   
      The first argument of the **ConnectionEventHandler** constructor is a reference to the class that contains the event handler named in the second argument.  
   
-3.  Add your event handler to a list of handlers designated to process a particular type of event. Use the method with a name such as **addOn***EventName*(*handler*).  
+3.  Add your event handler to a list of handlers designated to process a particular type of event. Use the method with a name such as **addOn**_EventName_(*handler*).  
   
 4.  ADO/WFC internally implements all the ADO event handlers. Therefore, an event caused by a **Connection** or **Recordset** operation is intercepted by an ADO/WFC event handler.  
   
@@ -52,7 +52,7 @@ ADO for Windows Foundation Classes (ADO/WFC) builds on the ADO event model and p
   
 6.  Return from your event handler to the ADO/WFC handler for the ADO event. ADO/WFC copies pertinent ADO/WFC event data members back to the ADO event parameters, and then the ADO event handler returns.  
   
-7.  When you are finished processing, remove your handler from the list of ADO/WFC event handlers. Use the method with a name such as **removeOn***EventName*(*handler*).  
+7.  When you are finished processing, remove your handler from the list of ADO/WFC event handlers. Use the method with a name such as **removeOn**_EventName_(*handler*).  
   
 ## See Also  
  [ADO Event Handler Summary](../../../ado/guide/data/ado-event-handler-summary.md)   
diff --git a/docs/analytics-platform-system/dwloader.md b/docs/analytics-platform-system/dwloader.md
@@ -138,7 +138,7 @@ Examples:
   
 `rv=25`  
   
-**-S***target_appliance*  
+**-S** *target_appliance*  
 Specifies the SQL Server PDW appliance that will receive the loaded data.  
   
 *For Infiniband connections*, *target_appliance* is specified as <appliance-name>-SQLCTL01. To configure this named connection, see [Configure InfiniBand Network Adapters](configure-infiniband-network-adapters.md).  
@@ -154,7 +154,7 @@ For more information about this install option, see [Install dwloader Command-Li
 **-T** *target_database_name.*[*schema*].*table_name*  
 The three-part name for the destination table.  
   
-**-I***source_data_location*  
+**-I** *source_data_location*  
 The location of one or more source files to load. Each source file must be a text file or a text file that is compressed with gzip. Only one source file can be compressed into each gzip file.  
   
 To format a source file:  
diff --git a/docs/database-engine/configure-windows/scm-services-change-the-service-startup-account.md b/docs/database-engine/configure-windows/scm-services-change-the-service-startup-account.md
@@ -54,7 +54,7 @@ ms.author: mikeray
   
 3.  In the details pane, right-click the name of the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] instance for which you want to change the service startup account, and then click **Properties**.  
   
-4.  In the **SQL Server \<***instancename***> Properties** dialog box, click the **Log On** tab, and select a **Log on as** account type.  
+4.  In the **SQL Server \<**_instancename_**> Properties** dialog box, click the **Log On** tab, and select a **Log on as** account type.  
   
 5.  After selecting the new service startup account, click **OK**.  
   
diff --git a/docs/database-engine/configure-windows/scm-services-set-an-instance-to-start-automatically.md b/docs/database-engine/configure-windows/scm-services-set-an-instance-to-start-automatically.md
@@ -37,7 +37,7 @@ ms.author: mikeray
   
 3.  In the details pane, right-click the name of the instance you want to start automatically, and then click **Properties**.  
   
-4.  In the **SQL Server \<***instancename***> Properties** dialog box, set **Start Mode** to **Automatic**.  
+4.  In the **SQL Server \<**_instancename_**> Properties** dialog box, set **Start Mode** to **Automatic**.  
   
 5.  Click **OK**, and then close [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Configuration Manager.  
   
diff --git a/docs/database-engine/database-mirroring/database-mirroring-monitor-status-page.md b/docs/database-engine/database-mirroring/database-mirroring-monitor-status-page.md
@@ -88,7 +88,7 @@ ms.author: mikeray
 -   **High safety with automatic failover (synchronous)**  
   
 ## Remarks  
- Members of the **dbm_monitor** fixed database role can view the existing mirroring status by using either Database Mirroring Monitor or the **sp_dbmmonitorresults** stored procedure. But these users cannot update the status table. They depend on the **Database Mirroring Monitor Job**to update the status table at regular intervals. To learn the age of the displayed status a user can look at the times in the **Principal log (***\<time>***)** and **Mirror log (***\<time>***)** labels.  
+ Members of the **dbm_monitor** fixed database role can view the existing mirroring status by using either Database Mirroring Monitor or the **sp_dbmmonitorresults** stored procedure. But these users cannot update the status table. They depend on the **Database Mirroring Monitor Job**to update the status table at regular intervals. To learn the age of the displayed status a user can look at the times in the **Principal log (**_\<time>_**)** and **Mirror log (**_\<time>_**)** labels.  
   
  If this job does not exist or [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent is stopped, the status becomes increasingly stale and may no longer reflect the configuration of the mirroring session. For example, after a failover, the partners might appear to share the same role-principal or mirror, or the current principal server might be shown as the mirror, while the current mirror server is shown as the principal.  
   
diff --git a/docs/database-engine/database-mirroring/example-setting-up-database-mirroring-using-certificates-transact-sql.md b/docs/database-engine/database-mirroring/example-setting-up-database-mirroring-using-certificates-transact-sql.md
@@ -256,7 +256,7 @@ ms.author: mikeray
     ```  
   
     > [!NOTE]  
-    >  If you intend to run in high-safety mode with automatic failover, leave transaction safety set to FULL (the default setting) and add the witness as soon as possible after executing the second SET PARTNER **'***partner_server***'** statement. Note that the witness must first be configured for outbound and inbound connections.  
+    >  If you intend to run in high-safety mode with automatic failover, leave transaction safety set to FULL (the default setting) and add the witness as soon as possible after executing the second SET PARTNER **'**_partner_server_**'** statement. Note that the witness must first be configured for outbound and inbound connections.  
   
  [&#91;Top of Example&#93;](#ExampleH2)  
   
diff --git a/docs/database-engine/database-mirroring/monitoring-database-mirroring-sql-server.md b/docs/database-engine/database-mirroring/monitoring-database-mirroring-sql-server.md
@@ -125,7 +125,7 @@ ms.author: mikeray
      System administrators can use the **sp_dbmmonitorresults** system stored procedure to view and, optionally, to update the status table, if it has not been updated within the previous 15 seconds. This procedure calls the **sp_dbmmonitorupdate** procedure and returns one or more history rows, depending on the amount requested in the procedure call. For information about the status in its results set, see [sp_dbmmonitorresults &#40;Transact-SQL&#41;](../../relational-databases/system-stored-procedures/sp-dbmmonitorresults-transact-sql.md).  
   
 #### Monitoring Database Mirroring Status (by dbm_monitor Members)  
- As mentioned, the first time **sp_dbmmonitorupdate** runs, it creates the **dbm_monitor** fixed database role in the **msdb** database. Members of the **dbm_monitor** fixed database role can view the existing mirroring status by using either Database Mirroring Monitor or the **sp_dbmmonitorresults** stored procedure. But these users cannot update the status table. To learn the age of the displayed status a user can look at the times in the **Principal log (***\<time>***)** and **Mirror log (***\<time>***)** labels on the **Status** page.  
+ As mentioned, the first time **sp_dbmmonitorupdate** runs, it creates the **dbm_monitor** fixed database role in the **msdb** database. Members of the **dbm_monitor** fixed database role can view the existing mirroring status by using either Database Mirroring Monitor or the **sp_dbmmonitorresults** stored procedure. But these users cannot update the status table. To learn the age of the displayed status a user can look at the times in the **Principal log (**_\<time>_**)** and **Mirror log (**_\<time>_**)** labels on the **Status** page.  
   
  Members of the **dbm_monitor** fixed database role depend on the **Database Mirroring Monitor Job** to update the status table at regular intervals. If the job does not exist or [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent is stopped, the status becomes increasingly stale and may no longer reflect the configuration of the mirroring session. For example, after a failover, the partners might appear to share the same role-principal or mirror, or the current principal server might be shown as the mirror, while the current mirror server is shown as the principal.  
   
diff --git a/docs/relational-databases/logs/view-offline-log-files.md b/docs/relational-databases/logs/view-offline-log-files.md
@@ -69,7 +69,7 @@ ms.author: "mathoma"
   
     3.  Enter the remote computer name, and then click **OK**.  
   
-3.  Right-click **WMI Control (Local)** or **WMI Control (***RemoteComputerName***)**, and then click **Properties**.  
+3.  Right-click **WMI Control (Local)** or **WMI Control (**_RemoteComputerName_**)**, and then click **Properties**.  
   
 4.  In the **WMI Control Properties** dialog box, click the **Security** tab.  
   
diff --git a/docs/relational-databases/replication/security/secure-the-subscriber.md b/docs/relational-databases/replication/security/secure-the-subscriber.md
@@ -51,7 +51,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2014||=sqlallproducts-allversio
  For more information, see [Create an Updatable Subscription to a Transactional Publication](../../../relational-databases/replication/publish/create-an-updatable-subscription-to-a-transactional-publication.md) and [View and Modify Replication Security Settings](../../../relational-databases/replication/security/view-and-modify-replication-security-settings.md).  
   
 > [!IMPORTANT]  
->  The account specified for the connection should only be granted permission to insert, update, and delete data on the views that replication creates in the publication database; it should not be given any additional permissions. Grant permissions on views in the publication database that are named in the form **syncobj_***\<HexadecimalNumber>* to the account you configured at each Subscriber.  
+>  The account specified for the connection should only be granted permission to insert, update, and delete data on the views that replication creates in the publication database; it should not be given any additional permissions. Grant permissions on views in the publication database that are named in the form **syncobj_**_\<HexadecimalNumber>_ to the account you configured at each Subscriber.  
   
 ## Queued Updating Subscriptions  
  When you configure queued updating subscriptions, there are two areas to keep in mind that relate to security:  
