Merge pull request #8585 from Saisang/sai-fixMultipleAsterisk-1218-2

fix multiple asterisk 3rd batch part 2

Author: Jak-MS

docs/2014/database-engine/availability-groups/windows/specify-endpoint-url-adding-or-modifying-availability-replica.md

@@ -33,23 +33,23 @@ manager: craigg
 ##  <a name="SyntaxOfURL"></a> Syntax for an Endpoint URL  
  The syntax for an endpoint URL is of the form:  
 
- TCP**://***\<system-address>***:***\<port>*  
+ TCP<strong>://</strong>*\<system-address>*<strong>:<strong>*\<port>*  
 
  where  
 
 -   *\<system-address>* is a string that unambiguously identifies the target computer system. Typically, the server address is a system name (if the systems are in the same domain), a fully qualified domain name, or an IP address:  
 
     -   Because the nodes of Windows Server Failover Clustering (WSFC) cluster are the same domain, you can use the name of the computer system; for example, `SYSTEM46`.  
 
-    -   To use an IP address, it must be unique in your environment. We recommend that you use an IP address only if it is static. The IP address can be IP Version 4 (IPv4) or IP Version 6 (IPv6). An IPv6 address must be enclosed within square brackets, for example: **[***<IPv6_address>***]**.  
+    -   To use an IP address, it must be unique in your environment. We recommend that you use an IP address only if it is static. The IP address can be IP Version 4 (IPv4) or IP Version 6 (IPv6). An IPv6 address must be enclosed within square brackets, for example: **[**_<IPv6_address>_**]**.  
 
          To learn the IP address of a system, at the Windows command prompt, enter the **ipconfig** command.  
 
     -   The fully qualified domain name is guaranteed to work. This is a locally defined address string that takes different forms in different places. Often, but not always, a fully qualified domain name is a compound name that includes the computer name and a series of period-separated domain segments of the form:  
 
-         *computer_name* **.** *domain_segment*[...**.***domain_segment*]  
+         _computer_name_ **.** _domain_segment_[...**.**_domain_segment_]  
 
-         where *computer_name i*s the network name of the computer running the server instance, and *domain_segment*[...**.***domain_segment*] is the remaining domain information of the server; for example: `localinfo.corp.Adventure-Works.com`.  
+         where *computer_name i*s the network name of the computer running the server instance, and *domain_segment*[...**.**_domain_segment_] is the remaining domain information of the server; for example: `localinfo.corp.Adventure-Works.com`.  
 
          The content and number of domain segments are determined within the company or organization. For more information, see [Finding the Fully Qualified Domain Name](#Finding_FQDN), later in this topic.  
 
@@ -98,7 +98,7 @@ manager: craigg
   
  To form the fully qualified domain name, concatenate the values of*<host_name>* and *<Primary_Dns_Suffix>* as follows:  
   
- *<host_name>* **.** *<Primary_Dns_Suffix>*  
+ _<host_name>_ **.** _<Primary_Dns_Suffix>_  
   
  For example, the IP configuration  
   

docs/2014/database-engine/database-mirroring/specify-a-server-network-address-database-mirroring.md

@@ -26,23 +26,23 @@ manager: craigg
 ##  <a name="Syntax"></a> Syntax for a Server Network Address  
  The syntax for a server network address is of the form:  
 
- TCP**://***\<system-address>***:***\<port>*  
+ TCP<strong>://</strong>*\<system-address>*<strong>:<strong>*\<port>* 
 
  where  
 
 -   *\<system-address>* is a string that unambiguously identifies the destination computer system. Typically, the server address is a system name (if the systems are in the same domain), a fully qualified domain name, or an IP address:  
 
     -   If the systems are the same domain, you can use the name of the computer system; for example, `SYSTEM46`.  
 
-    -   To use an IP address, it must be unique in your environment. We recommend that you use an IP address only if it is static. The IP address can be IP Version 4 (IPv4) or IP Version 6 (IPv6). An IPv6 address must be enclosed within square brackets, for example: **[***<IPv6_address>***]**.  
+    -   To use an IP address, it must be unique in your environment. We recommend that you use an IP address only if it is static. The IP address can be IP Version 4 (IPv4) or IP Version 6 (IPv6). An IPv6 address must be enclosed within square brackets, for example: **[**_<IPv6_address>_**]**.  
 
          To learn the IP address of a system, at the Windows command prompt, enter the **ipconfig** command.  
 
     -   The fully qualified domain name is guaranteed to work. This is a locally defined address string that different forms in different places. Often, but not always, a fully qualified domain name is a compound name that includes the computer name and a series of period-separated domain segments of the form:  
 
-         *computer_name* **.** *domain_segment*[...**.***domain_segment*]  
+         _computer_name_ **.** _domain_segment_[...**.**_domain_segment_]  
 
-         where *computer_name i*s the network name of the computer running the server instance, and *domain_segment*[...**.***domain_segment*] is the remaining domain information of the server; for example: `localinfo.corp.Adventure-Works.com`.  
+         where *computer_name i*s the network name of the computer running the server instance, and *domain_segment*[...**.**_domain_segment_] is the remaining domain information of the server; for example: `localinfo.corp.Adventure-Works.com`.  
 
          The content and number of domain segments are determined within the company or organization. If you do not know the fully qualified domain name for your server, see your system administrator.  
 
@@ -102,7 +102,7 @@ ALTER DATABASE AdventureWorks SET PARTNER ='tcp://[2001:4898:23:1002:20f:1fff:fe
   
  To form the fully qualified domain name, concatenate the values of*<host_name>* and *<Primary_Dns_Suffix>* as follows:  
   
- *<host_name>* **.** *<Primary_Dns_Suffix>*  
+ _<host_name>_ **.** _<Primary_Dns_Suffix>_  
   
  For example, the IP configuration  
   

docs/2014/relational-databases/indexes/specify-fill-factor-for-an-index.md

@@ -73,7 +73,7 @@ manager: craigg
 
 7.  Click **Close**.  
 
-8.  On the **File** menu, select **Save***table_name*.  
+8.  On the **File** menu, select **Save**_table_name_.  
 
 #### To specify a fill factor in an index by using Object Explorer  
 

docs/2014/relational-databases/spatial/spatial-indexes-overview.md

@@ -121,7 +121,7 @@ manager: craigg
 >  You can explicitly specify this tessellation scheme by using the USING (GEOMETRY_AUTO_GRID/GEOMETRY_GRID) clause of the [CREATE SPATIAL INDEX](/sql/t-sql/statements/create-spatial-index-transact-sql)[!INCLUDE[tsql](../../../includes/tsql-md.md)] statement.  
   
 ##### The Bounding Box  
- Geometric data occupies a plane that can be infinite. In [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], however, a spatial index requires a finite space. To establish a finite space for decomposition, the geometry grid tessellation scheme requires a rectangular *bounding box*. The bounding box is defined by four coordinates, `(`*x-min***,***y-min*`)` and `(`*x-max***,***y-max*`)`, which are stored as properties of the spatial index. These coordinates represent the following:  
+ Geometric data occupies a plane that can be infinite. In [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)], however, a spatial index requires a finite space. To establish a finite space for decomposition, the geometry grid tessellation scheme requires a rectangular *bounding box*. The bounding box is defined by four coordinates, `(`_x-min_**,**_y-min_`)` and `(`_x-max_**,**_y-max_`)`, which are stored as properties of the spatial index. These coordinates represent the following:  
 
 -   *x-min* is the x-coordinate of the lower-left corner of the bounding box.  
 
@@ -134,11 +134,11 @@ manager: craigg
 > [!NOTE]  
 >  These coordinates are specified by the BOUNDING_BOX clause of the [CREATE SPATIAL INDEX](/sql/t-sql/statements/create-spatial-index-transact-sql)[!INCLUDE[tsql](../../../includes/tsql-md.md)] statement.  
   
- The `(`*x-min***,***y-min*`)` and `(`*x-max***,***y-max*`)` coordinates determine the placement and dimensions of the bounding box. The space outside of the bounding box is treated as a single cell that is numbered 0.  
+ The `(`_x-min_**,**_y-min_`)` and `(`_x-max_**,**_y-max_`)` coordinates determine the placement and dimensions of the bounding box. The space outside of the bounding box is treated as a single cell that is numbered 0.  
 
  The spatial index decomposes the space inside the bounding box. The level-1 grid of the grid hierarchy fills the bounding box. To place a geometric object in the grid hierarchy, the spatial index compares the coordinates of the object to the bounding-box coordinates.  
 
- The following illustration shows the points defined by the `(`*x-min***,***y-min*`)` and `(`*x-max***,***y-max*`)` coordinates of the bounding box. The top-level of the grid hierarchy is shown as a 4x4 grid. For the purpose of illustration, the lower levels are omitted. The space outside of the bounding box is indicated by a zero (0). Note that object 'A' extends partly beyond the box, and object 'B' lies completely outside the box in cell 0.  
+ The following illustration shows the points defined by the `(`_x-min_**,**_y-min_`)` and `(`_x-max_**,**_y-max_`)` coordinates of the bounding box. The top-level of the grid hierarchy is shown as a 4x4 grid. For the purpose of illustration, the lower levels are omitted. The space outside of the bounding box is indicated by a zero (0). Note that object 'A' extends partly beyond the box, and object 'B' lies completely outside the box in cell 0.  
 
  ![Bounding box showing coordinates and cell 0.](../../database-engine/media/spndx-bb-4x4-objects.gif "Bounding box showing coordinates and cell 0.")  
 

docs/2014/relational-databases/stored-procedures/specify-parameters.md

@@ -57,10 +57,10 @@ GO
  Explicitly naming the parameters and assigning the appropriate values to each parameter in a procedure call allows the parameters to be supplied in any order. For example, if the procedure **my_proc** expects three parameters named **\@first**, **\@second**, and **\@third**, the values passed to the procedure can be assigned to the parameter names, such as: `EXECUTE my_proc @second = 2, @first = 1, @third = 3;`  
 
 > [!NOTE]
->  If one parameter value is supplied in the form **/@parameter =***value*, all subsequent parameters must be supplied in this manner. If the parameter values are not passed in the form **\@parameter =***value*, the values must be supplied in the identical order (left to right) as the parameters are listed in the CREATE PROCEDURE statement.  
+>  If one parameter value is supplied in the form **\@parameter =**_value_, all subsequent parameters must be supplied in this manner. If the parameter values are not passed in the form **\@parameter =**_value_, the values must be supplied in the identical order (left to right) as the parameters are listed in the CREATE PROCEDURE statement.  
 > 
 > [!WARNING]
->  Any parameter passed in the form **\@parameter =***value* with the parameter misspelled, will cause [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to generate an error and prevent procedure execution.  
+>  Any parameter passed in the form **\@parameter =**_value_ with the parameter misspelled, will cause [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] to generate an error and prevent procedure execution.  
   
 ## Specifying Parameter Data Types  
  Parameters must be defined with a data type when they are declared in a CREATE PROCEDURE statement. The data type of a parameter determines the type and range of values that are accepted for the parameter when the procedure is called. For example, if you define a parameter with a `tinyint` data type, only numeric values ranging from 0 to 255 are accepted when passed into that parameter. An error is returned if a procedure is executed with a value incompatible with the data type.  
@@ -120,7 +120,7 @@ EXEC Sales.usp_GetSalesYTD N'Blythe';
 GO  
 ```  
 
- Although parameters for which defaults have been supplied can be omitted, the list of parameters can only be truncated. For example, if a procedure has five parameters, both the fourth and the fifth parameters can be omitted. However the fourth parameter cannot be skipped as long as the fifth parameter is included, unless the parameters are supplied in the form **\@parameter =***value*.  
+ Although parameters for which defaults have been supplied can be omitted, the list of parameters can only be truncated. For example, if a procedure has five parameters, both the fourth and the fifth parameters can be omitted. However the fourth parameter cannot be skipped as long as the fifth parameter is included, unless the parameters are supplied in the form **\@parameter =**_value_.  
 
 ## Specifying Parameter Direction  
  The direction of a parameter is either input, a value is passed into the body of the procedure, or output, the procedure returns a value to the calling program. The default is an input parameter.  
@@ -161,7 +161,7 @@ GO
  Execute `usp_GetList` to return a list of [!INCLUDE[ssSampleDBCoShort](../../includes/sssampledbcoshort-md.md)] products (Bikes) that cost less than $700. The OUTPUT parameters **\@cost** and **\@compareprices** are used with control-of-flow language to return a message in the **Messages** window.  
 
 > [!NOTE]  
->  The OUTPUT variable must be defined during the procedure creation and also during the use of the variable. The parameter name and variable name do not have to match. However, the data type and parameter positioning must match (unless **\@listprice=** *variable* is used).  
+>  The OUTPUT variable must be defined during the procedure creation and also during the use of the variable. The parameter name and variable name do not have to match. However, the data type and parameter positioning must match (unless **\@listprice=** _variable_ is used).  
   
 ```  
 DECLARE @ComparePrice money, @Cost money ;  

docs/2014/relational-databases/tables/specify-computed-columns-in-a-table.md

@@ -60,7 +60,7 @@ manager: craigg
   
 5.  Indicate whether the data is persisted by choosing **Yes** or **No** from the drop-down for the **Is Persisted** child property.  
 
-6.  On the **File** menu, click **Save***table name*.  
+6.  On the **File** menu, click **Save**_table name_.  
 
 #### To add a computed column definition to an existing column  
 

docs/2014/relational-databases/tables/specify-default-values-for-columns.md

@@ -65,7 +65,7 @@ manager: craigg
     > [!NOTE]  
     >  To enter a numeric default value, enter the number. For an object or function enter its name. For an alphanumeric default enter the value inside single quotes.  
   
-4.  On the **File** menu, click **Save***table name*.  
+4.  On the **File** menu, click **Save**_table name_.  
 
 ##  <a name="TsqlProcedure"></a> Using Transact-SQL  
 

docs/2014/ssms/agent/set-service-startup-account-sql-server-agent-sql-server-configuration-manager.md

@@ -65,9 +65,9 @@ manager: craigg
 
 5.  In [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Configuration Manager, in the console pane, select **SQL Server Services**.  
 
-6.  In the details pane, right-click **SQL Server Agent***(server_name)*, where *server_name* is the name of the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent instance for which you want to change the service startup account, and select **Properties**.  
+6.  In the details pane, right-click **SQL Server Agent**_(server_name)_, where *server_name* is the name of the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent instance for which you want to change the service startup account, and select **Properties**.  
 
-7.  In the **SQL Server Agent***(server_name)* **Properties** dialog box, in the **Log On** tab, select one of the following options under **Log on as**:  
+7.  In the **SQL Server Agent**_(server_name)_ **Properties** dialog box, in the **Log On** tab, select one of the following options under **Log on as**:  
 
     -   **Built-in account**: select this option if your jobs require resources from the local server only. For information about how to choose a Windows built-in account type, see [Selecting an Account for SQL Server Agent Service.](https://msdn.microsoft.com/library/ms191543.aspx)  
 

docs/2014/ssms/agent/set-sql-server-connection-for-sql-server-agent-service-ssms.md

@@ -60,7 +60,7 @@ manager: craigg
 
 2.  Right-click **SQL Server Agent** and select **Properties**.  
 
-3.  In the **SQL Server Agent Properties***sever_name* dialog box, under **Select a page**, click **Connection**.  
+3.  In the **SQL Server Agent Properties**_sever_name_ dialog box, under **Select a page**, click **Connection**.  
 
 4.  Under **SQL Server connection**, select **Use Windows Authentication** to enable [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] Agent to connect to an instance of the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] [!INCLUDE[ssDE](../../includes/ssde-md.md)] with [!INCLUDE[msCoName](../../includes/msconame-md.md)] Windows Authentication. Connections to [!INCLUDE[ssVersion2005](../../includes/ssversion2005-md.md)] and later databases require Windows Authentication.  
 

docs/2014/ssms/visual-db-tools/spatial-indexes-dialog-box-visual-database-tools.md

@@ -103,7 +103,7 @@ manager: craigg
  **Page Locks Allowed**  
  Specifies whether page-level locking is allowed on this index. Allowing or disallowing page-level locking affects database performance.  
 
- **Re-compute**  **Statistics**  
+ **Re-compute  Statistics**  
  Specifies whether to compute new statistics when the index is created. Recomputing statistics slows the building of indexes but usually improves query performance.  
 
  **Row Locks Allowed**