Merge pull request #8518 from Saisang/sai-fixMultipleAsterisk-part6

fix multiple asterisks 12/17 - 4

Author: GitHubber17

docs/2014/sql-server/install/user-defined-functions-are-not-allowed-in-system-function-schema.md

@@ -49,7 +49,7 @@ manager: craigg
 
 4.  Replace references to **system_function_schema** with **dbo** in all scripts that contain user-defined function DDL statements.  
 
-5.  Modify scripts that invoke these functions to use either the two-part name dbo**.***function_name*, or the three-part name *database_name***.**dbo.*function_name*.  
+5.  Modify scripts that invoke these functions to use either the two-part name dbo**.**_function_name_, or the three-part name _database_name_**.**dbo.*function_name*.  
 
  For more information, see the following topics in SQL Server Books Online:  
 

docs/ado/guide/appendixes/visual-c-ado-programming.md

@@ -68,6 +68,7 @@ variable = objectPtr->GetProperty;  // get property value
  For example, the **Command** object **ActiveConnection** property is declared with an alternative syntax for **Get**_ActiveConnection_ and **PutRef**_ActiveConnection_. The **PutRef**- syntax is a good choice because in practice, you will typically want to put an open **Connection** object (that is, a **Connection** object pointer) in this property. On the other hand, the **Recordset** object has **Get**-, **Put**-, and **PutRef**_ActiveConnection_ operations, but no alternative syntax.  
   
 ## Collections, the GetItem Method, and the Item Property  
+
  ADO defines several collections, including **Fields**, **Parameters**, **Properties**, and **Errors**. In Visual C++, the **GetItem(_index_)** method returns a member of the collection. *Index* is a **Variant**, the value of which is either a numeric index of the member in the collection, or a string containing the name of the member.  
   
  The **__declspec(property...)** compiler directive declares the **Item** property as an alternative syntax to each collection's fundamental **GetItem()** method. The alternative syntax uses square brackets and looks similar to an array reference. In general, the two forms look like the following:  

docs/ado/guide/data/required-providers-for-data-shaping.md

@@ -20,7 +20,7 @@ Data shaping typically requires two providers. The service provider, [Data Shapi
 
  The name of the service provider (MSDataShape) can be specified as the value of the [Connection](../../../ado/reference/ado-api/connection-object-ado.md) object [Provider](../../../ado/reference/ado-api/provider-property-ado.md) property or the connection string keyword "Provider=MSDataShape;".  
 
- The name of the data provider can be specified as the value of the **Data Provider** dynamic property, which is added to the **Connection** object [Properties](../../../ado/reference/ado-api/properties-collection-ado.md) collection by the Data Shaping Service for OLE DB, or the connection string keyword "**Data Provider=***provider*".  
+ The name of the data provider can be specified as the value of the **Data Provider** dynamic property, which is added to the **Connection** object [Properties](../../../ado/reference/ado-api/properties-collection-ado.md) collection by the Data Shaping Service for OLE DB, or the connection string keyword "**Data Provider=**_provider_".  
 
  No data provider is required if the **Recordset** is not populated (for example, as in a fabricated **Recordset** where columns are created with the NEW keyword). In that case, specify "**Data Provider=**none;".  
 

docs/ado/guide/data/types-of-events.md

@@ -22,15 +22,15 @@ manager: craigg
 There are two basic types of events. "Will Events," which are called before an operation starts, usually include "Will" in their names - for example, **WillChangeRecordset** or **WillConnect**. Events that are called after an event has been completed usually include "Complete" in their names - for example, **RecordChangeComplete** or **ConnectComplete**. Exceptions exist - such as **InfoMessage** - but these occur after the associated operation has completed.  
 
 ## Will Events  
- Event handlers called before the operation starts offer you the opportunity to examine or modify the operation parameters, and then either cancel the operation or allow it to complete. These event-handler routines usually have names of the form **Will*Event***.  
+ Event handlers called before the operation starts offer you the opportunity to examine or modify the operation parameters, and then either cancel the operation or allow it to complete. These event-handler routines usually have names of the form <strong>Will*Event*</strong>.  
 
 ## Complete Events  
- Event handlers called after an operation completes can notify your application that an operation has concluded. Such an event handler is also notified when a Will event handler cancels a pending operation. These event-handler routines usually have names of the form ***Event*Complete**.  
+ Event handlers called after an operation completes can notify your application that an operation has concluded. Such an event handler is also notified when a Will event handler cancels a pending operation. These event-handler routines usually have names of the form <strong>*Event*Complete</strong>.  
 
  Will and Complete events are typically used in pairs.  
 
 ## Other Events  
- The other event handlers - that is, events whose names are not of the form **Will*Event*** or ***Event*Complete** - are called only after an operation completes. These events are **Disconnect**, **EndOfRecordset**, and **InfoMessage**.  
+ The other event handlers - that is, events whose names are not of the form <strong>Will*Event*</strong> or <strong>*Event*Complete</strong> - are called only after an operation completes. These events are **Disconnect**, **EndOfRecordset**, and **InfoMessage**.  
 
 ## See Also  
  [ADO Event Handler Summary](../../../ado/guide/data/ado-event-handler-summary.md)   

docs/ado/guide/remote-data-service/understanding-the-customization-file.md

@@ -49,7 +49,7 @@ identifier
 
  A particular section is used under the following circumstances:  
 
--   A **connect** section is used if the value part of the client connect string keyword, "**Data Source=***value*", matches a **connect** section identifier*.*  
+-   A **connect** section is used if the value part of the client connect string keyword, "**Data Source=**_value_", matches a **connect** section identifier*.*  
 
 -   An **sql** section is used if the client command string contains a string that matches an **sql** section identifier.  
 

docs/ado/reference/ado-api/willexecute-event-ado.md

@@ -59,7 +59,7 @@ WillExecute Source, CursorType, LockType, Options, adStatus, pCommand, pRecordse
  **WillExecute** allows you to examine and modify the pending execution parameters. This event may return a request that the pending command be canceled.  
 
 > [!NOTE]
->  If the original source for a **Command** is a stream specified by the [CommandStream Property (ADO)](../../../ado/reference/ado-api/commandstream-property-ado.md) property, assigning a new string to the **WillExecute***Source* parameter changes the source of the **Command**. The **CommandStream** property will be cleared and the [CommandText Property (ADO)](../../../ado/reference/ado-api/commandtext-property-ado.md) property will be updated with the new source. The original stream specified by **CommandStream** will be released and cannot be accessed.  
+>  If the original source for a **Command** is a stream specified by the [CommandStream Property (ADO)](../../../ado/reference/ado-api/commandstream-property-ado.md) property, assigning a new string to the **WillExecute**_Source_ parameter changes the source of the **Command**. The **CommandStream** property will be cleared and the [CommandText Property (ADO)](../../../ado/reference/ado-api/commandtext-property-ado.md) property will be updated with the new source. The original stream specified by **CommandStream** will be released and cannot be accessed.  
   
  If the dialect of the new source string differs from the original setting of the [Dialect Property](../../../ado/reference/ado-api/dialect-property.md) property (which corresponded to the **CommandStream**), the correct dialect must be specified by setting the **Dialect** property of the command object referenced by *pCommand*.  
 

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

@@ -21,13 +21,13 @@ To perform these steps, you will need:
 
 -   An Analytics Platform System login with permissions to access the Admin Console to monitor the appliance.  
 
--   The Domain Administrator account to login to the *<appliance_domain>***-HST01** node.  
+-   The Domain Administrator account to login to the <em><appliance_domain></em>**-HST01** node.  
 
 -   The Knowledge Base article number for the hotfix to uninstall.  
 
 ## <a name="HowToUninstallPDW"></a>To uninstall a SQL Server PDW hotfix  
 
-1.  Log on to the *<appliance_domain>***-HST01** node as the Fabric Domain Administrator.  
+1.  Log on to the <em><appliance_domain></em>**-HST01** node as the Fabric Domain Administrator.  
 
 2.  Use the Run as Administrator option to open a Command Prompt.  
 

docs/analytics-platform-system/uninstall-microsoft-updates.md

@@ -21,11 +21,11 @@ To perform these steps, you will need:
 
 -   An Analytics Platform System login with permissions to access the Admin Console to monitor the appliance.  
 
--   Knowledge of the Fabric Domain Administrator account to log in to the *<Fabric Domain>***-HST01** node.  
+-   Knowledge of the Fabric Domain Administrator account to log in to the <em><Fabric Domain></em>**-HST01** node.  
 
 ## <a name="HowToUninstallMSFT"></a>To uninstall Microsoft updates  
 
-1.  Log in to the *<Fabric Domain>***-HST01** node as the Fabric Domain Administrator.  
+1.  Log in to the <em><Fabric Domain></em>**-HST01** node as the Fabric Domain Administrator.  
 
 2.  To uninstall all updates that are approved for WSUS to uninstall, open a Command Prompt window and enter the following command. Replace the placeholder items *<  >* with the appropriate information.  
 

docs/database-engine/availability-groups/windows/use-the-fail-over-availability-group-wizard-sql-server-management-studio.md

@@ -54,7 +54,7 @@ manager: craigg
 
 4.  The information presented by the **Introduction** page depends on whether any secondary replica is eligible for a planned failover. If this page says, "**Perform a planned failover for this availability group**", you can failover the availability group without data loss.  
 
-5.  On the **Select New Primary Replica** page, you can view the status of the current primary replica and of the WSFC quorum, before you choose the secondary replica that will become the new primary replica (the *failover target*). For a planned manual failover, be sure to select a secondary replica whose **Failover Readiness** value is "**No data loss**". For a forced failover, for all the possible failover targets, this value will be "**Data loss, Warnings(***#***)**", where *#* indicates the number of warnings that exist for a given secondary replica. To view the warnings for a given failover target, click its "Failover Readiness" value.  
+5.  On the **Select New Primary Replica** page, you can view the status of the current primary replica and of the WSFC quorum, before you choose the secondary replica that will become the new primary replica (the *failover target*). For a planned manual failover, be sure to select a secondary replica whose **Failover Readiness** value is "**No data loss**". For a forced failover, for all the possible failover targets, this value will be "**Data loss, Warnings(**_#_**)**", where *#* indicates the number of warnings that exist for a given secondary replica. To view the warnings for a given failover target, click its "Failover Readiness" value.  
 
      For more information, see [Select New Primary Replica page](#SelectNewPrimaryReplica), later in this topic.  
 
@@ -145,7 +145,7 @@ manager: craigg
 |Value|Description|  
 |-----------|-----------------|  
 |**No data loss**|This secondary replica currently supports planned failover. This value occurs only when a synchronous-commit mode secondary replica is currently synchronized with the primary replica.|  
-|**Data loss, Warnings(** *#* **)**|This secondary replica currently supports forced failover (with possible data loss). This value occurs whenever the secondary replica is not synchronized with the primary replica. Click the data-loss warnings link for information about the possible data loss.|  
+|**Data loss, Warnings(** _#_ **)**|This secondary replica currently supports forced failover (with possible data loss). This value occurs whenever the secondary replica is not synchronized with the primary replica. Click the data-loss warnings link for information about the possible data loss.|  
 
  **Refresh**  
  Click to update the grid.  

docs/database-engine/configure-windows/view-or-change-server-properties-sql-server.md

@@ -149,9 +149,9 @@ GO
 
 2.  In **SQL Server Configuration Manager**, click **SQL Server Services**.  
 
-3.  In the details pane, right-click **SQL Server (\<***instancename***>)**, and then click **Properties**.  
+3.  In the details pane, right-click **SQL Server (\<**_instancename_**>)**, and then click **Properties**.  
 
-4.  In the **SQL Server (\<***instancename***>) Properties** dialog box, change the server properties on the **Service** tab or the **Advanced** tab, and then click **OK**.  
+4.  In the **SQL Server (\<**_instancename_**>) Properties** dialog box, change the server properties on the **Service** tab or the **Advanced** tab, and then click **OK**.  
 
 ##  <a name="FollowUp"></a> Follow Up: After you change server properties  
  For some properties, the server might have to be restarted before the change can take effect.