Skip to content

Commit 6cecdf3

Browse files
SaisangSaisang
committed
bulk fix multiple asterisks
1 parent 07f14d1 commit 6cecdf3

18 files changed

Lines changed: 32 additions & 32 deletions

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

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ The ADO API Reference describes the functionality of the ADO application program
3434

3535
For each operation within a class (that is, a method or property call), there is a declaration to call the operation directly (that is, the "raw" form of the operation), and a declaration to call the raw operation and throw a COM error if the operation fails to execute successfully. If the operation is a property, there is usually a compiler directive that creates an alternative syntax for the operation that has syntax like Visual Basic.
3636

37-
Operations that retrieve the value of a property have names of the form, **Get***Property*. Operations that set the value of a property have names of the form, **Put***Property*. Operations that set the value of a property with a pointer to an ADO object have names of the form, **PutRef***Property*.
37+
Operations that retrieve the value of a property have names of the form, **Get**_Property_. Operations that set the value of a property have names of the form, **Put**_Property_. Operations that set the value of a property with a pointer to an ADO object have names of the form, **PutRef**_Property_.
3838

3939
You can get or set a property with calls of these forms:
4040

@@ -59,16 +59,16 @@ objectPtr->PutProperty(value);      // set property value
5959
variable = objectPtr->GetProperty;  // get property value
6060
```
6161
62-
The compiler will generate the appropriate **Get***-*, **Put**-, or **PutRef***Property* call based on what alternative syntax is declared and whether the property is being read or written.
62+
The compiler will generate the appropriate **Get***-*, **Put**-, or **PutRef**_Property_ call based on what alternative syntax is declared and whether the property is being read or written.
6363
6464
The **__declspec(property...)** compiler directive can only declare **get**, **put**, or **get** and **put** alternative syntax for a function. Read-only operations only have a **get** declaration; write-only operations only have a **put** declaration; operations that are both read and write have both **get** and **put** declarations.
6565
66-
Only two declarations are possible with this directive; however, each property may have three property functions: **Get***Property*, **Put***Property*, and **PutRef***Property*. In that case, only two forms of the property have the alternative syntax.
66+
Only two declarations are possible with this directive; however, each property may have three property functions: **Get**_Property_, **Put**_Property_, and **PutRef**_Property_. In that case, only two forms of the property have the alternative syntax.
6767
68-
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.
68+
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.
6969
7070
## Collections, the GetItem Method, and the Item Property
71-
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.
71+
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.
7272
7373
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:
7474
@@ -78,7 +78,7 @@ variable = objectPtr->GetProperty;  // get property value
7878
collectionPtr->Item[index];
7979
```
8080

81-
For example, assign a value to a field of a **Recordset** object, named ***rs***, derived from the **authors** table of the **pubs** database. Use the **Item()** property to access the third **Field** of the **Recordset** object **Fields** collection (collections are indexed from zero; assume the third field is named ***au_fname***). Then call the **Value()** method on the **Field** object to assign a string value.
81+
For example, assign a value to a field of a **Recordset** object, named **_rs_**, derived from the **authors** table of the **pubs** database. Use the **Item()** property to access the third **Field** of the **Recordset** object **Fields** collection (collections are indexed from zero; assume the third field is named **_au_fname_**). Then call the **Value()** method on the **Field** object to assign a string value.
8282

8383
This can be expressed in Visual Basic in the following four ways (the last two forms are unique to Visual Basic; other languages do not have equivalents):
8484

@@ -427,7 +427,7 @@ cn.Close
427427
End Sub
428428
```
429429

430-
This Visual C++ example demonstrates the **Get**/**Put**/**PutRef***Property*.
430+
This Visual C++ example demonstrates the **Get**/**Put**/**PutRef**_Property_.
431431

432432
#### Notes
433433
The following notes correspond to commented sections in the code example.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Data shaping typically requires two providers. The service provider, [Data Shapi
2020

2121
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;".
2222

23-
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*".
23+
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_".
2424

2525
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;".
2626

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,15 +22,15 @@ manager: craigg
2222
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.
2323

2424
## Will Events
25-
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***.
25+
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_**.
2626

2727
## Complete Events
28-
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**.
28+
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**.
2929

3030
Will and Complete events are typically used in pairs.
3131

3232
## Other Events
33-
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**.
33+
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**.
3434

3535
## See Also
3636
[ADO Event Handler Summary](../../../ado/guide/data/ado-event-handler-summary.md)

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ identifier
4949

5050
A particular section is used under the following circumstances:
5151

52-
- A **connect** section is used if the value part of the client connect string keyword, "**Data Source=***value*", matches a **connect** section identifier*.*
52+
- A **connect** section is used if the value part of the client connect string keyword, "**Data Source=**_value_", matches a **connect** section identifier*.*
5353

5454
- An **sql** section is used if the client command string contains a string that matches an **sql** section identifier.
5555

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ WillExecute Source, CursorType, LockType, Options, adStatus, pCommand, pRecordse
5959
**WillExecute** allows you to examine and modify the pending execution parameters. This event may return a request that the pending command be canceled.
6060

6161
> [!NOTE]
62-
> 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.
62+
> 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.
6363
6464
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*.
6565

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ manager: craigg
5454

5555
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.
5656

57-
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.
57+
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.
5858

5959
For more information, see [Select New Primary Replica page](#SelectNewPrimaryReplica), later in this topic.
6060

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -149,9 +149,9 @@ GO
149149

150150
2. In **SQL Server Configuration Manager**, click **SQL Server Services**.
151151

152-
3. In the details pane, right-click **SQL Server (\<***instancename***>)**, and then click **Properties**.
152+
3. In the details pane, right-click **SQL Server (\<**_instancename_**>)**, and then click **Properties**.
153153

154-
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**.
154+
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**.
155155

156156
## <a name="FollowUp"></a> Follow Up: After you change server properties
157157
For some properties, the server might have to be restarted before the change can take effect.

‎docs/database-engine/configure-windows/view-or-configure-remote-server-connection-options-sql-server.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ manager: craigg
4747

4848
1. In Object Explorer, right-click a server, and then click **Properties**.
4949

50-
2. In the **SQL Server Properties - \<***server_name***>** dialog box, click **Connections**.
50+
2. In the **SQL Server Properties - \<**_server_name_**>** dialog box, click **Connections**.
5151

5252
3. On the **Connections** page, review the **Remote server connections** settings, and modify them if necessary.
5353

‎docs/database-engine/database-mirroring/troubleshoot-database-mirroring-configuration-sql-server.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ manager: craigg
3333
|[Network access](#NetworkAccess)|Documents the requirement that each the server instance be able to access the ports of the other server instance or instances over TCP.|
3434
|[Mirror database preparation](#MirrorDbPrep)|Summarizes the requirements for preparing the mirror database to enable mirroring to start.|
3535
|[Failed create-file operation](#FailedCreateFileOp)|Describes how to respond to a failed create-file operation.|
36-
|[Starting mirroring by Using Transact-SQL](#StartDbm)|Describes the required order for ALTER DATABASE *database_name* SET PARTNER **='***partner_server***'** statements.|
36+
|[Starting mirroring by Using Transact-SQL](#StartDbm)|Describes the required order for ALTER DATABASE *database_name* SET PARTNER **='**_partner_server_**'** statements.|
3737
|[Cross-Database Transactions](#CrossDbTxns)|An automatic failover could lead to automatic and possibly incorrect resolution of in-doubt transactions. For this reason database mirroring does not support cross-database transactions.|
3838

3939
## <a name="Accounts"></a> Accounts
@@ -138,7 +138,7 @@ manager: craigg
138138
For more information, see [Removing Database Mirroring &#40;SQL Server&#41;](../../database-engine/database-mirroring/removing-database-mirroring-sql-server.md), [Prepare a Mirror Database for Mirroring &#40;SQL Server&#41;](../../database-engine/database-mirroring/prepare-a-mirror-database-for-mirroring-sql-server.md), [Establish a Database Mirroring Session Using Windows Authentication &#40;Transact-SQL&#41;](../../database-engine/database-mirroring/database-mirroring-establish-session-windows-authentication.md), [Use Certificates for a Database Mirroring Endpoint &#40;Transact-SQL&#41;](../../database-engine/database-mirroring/use-certificates-for-a-database-mirroring-endpoint-transact-sql.md), or [Establish a Database Mirroring Session Using Windows Authentication &#40;SQL Server Management Studio&#41;](../../database-engine/database-mirroring/establish-database-mirroring-session-windows-authentication.md).
139139
140140
## <a name="StartDbm"></a> Starting mirroring by Using Transact-SQL
141-
The order in which the ALTER DATABASE *database_name* SET PARTNER **='***partner_server***'** statements are issued is very important.
141+
The order in which the ALTER DATABASE *database_name* SET PARTNER **='**_partner_server_**'** statements are issued is very important.
142142
143143
1. The first statement must be run on the mirror server. When this statement is issued, the mirror server does not try to contact any other server instance. Instead, the mirror server instructs its database to wait until the mirror server has been contacted by the principal server.
144144

‎docs/odbc/reference/develop-app/types-of-applications.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ manager: craigg
2222
ODBC applications can be classified as follows:
2323

2424
- **Pure ODBC 2.**
25-
***x* Application** A 32-bit application that:
25+
**_x_ Application** A 32-bit application that:
2626

2727
- Calls only ODBC 2.*x* functions (including the ODBC 1.0 function **SQLSetParam**). These include ODBC 1.*x* applications that have been ported to 32-bit.
2828

@@ -31,10 +31,10 @@ ODBC applications can be classified as follows:
3131
- Has not been recompiled with ODBC 3.5 headers.
3232

3333
- **Pure ODBC 2.**
34-
***x* Recompiled Application** A pure ODBC 2.*x* application that has been recompiled using the ODBC 3.5 header files, by setting ODBCVER=0x0250.
34+
**_x_ Recompiled Application** A pure ODBC 2.*x* application that has been recompiled using the ODBC 3.5 header files, by setting ODBCVER=0x0250.
3535

3636
- **Pure ODBC 2.**
37-
***x* Unicode Application** A pure ODBC 2.*x* recompiled application that is Unicode-compliant and uses the SQL_WCHAR data type.
37+
**_x_ Unicode Application** A pure ODBC 2.*x* recompiled application that is Unicode-compliant and uses the SQL_WCHAR data type.
3838

3939
- **Pure Open Group and ISO**-**compliant ODBC Application** A 32-bit application that:
4040

0 commit comments

Comments
 (0)