Skip to content

Commit 8ac3a3b

Browse files
author
3836425+corob-msft@users.noreply.github.com
committed
Minimal acrolinx fixes
1 parent 2c9145c commit 8ac3a3b

2 files changed

Lines changed: 13 additions & 13 deletions

File tree

‎docs/atl/reference/composite-control-macros.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ These macros define event sink maps and entries.
1515
|[BEGIN_SINK_MAP](#begin_sink_map)|Marks the beginning of the event sink map for the composite control.|
1616
|[END_SINK_MAP](#end_sink_map)|Marks the end of the event sink map for the composite control.|
1717
|[SINK_ENTRY](#sink_entry)|Entry to the event sink map.|
18-
|[SINK_ENTRY_EX](#sink_entry_ex)|Entry to the event sink map with an additional parameter.|
18+
|[SINK_ENTRY_EX](#sink_entry_ex)|Entry to the event sink map with an extra parameter.|
1919
|[SINK_ENTRY_EX_P](#sink_entry_ex)| (Visual Studio 2017) Similar to SINK_ENTRY_EX except that it takes a pointer to iid.|
2020
|[SINK_ENTRY_INFO](#sink_entry_info)|Entry to the event sink map with manually supplied type information for use with [IDispEventSimpleImpl](../../atl/reference/idispeventsimpleimpl-class.md).|
2121
|[SINK_ENTRY_INFO_P](#sink_entry_info)| (Visual Studio 2017) Similar to SINK_ENTRY_INFO except that it takes a pointer to iid.|
@@ -43,7 +43,7 @@ BEGIN_SINK_MAP(_class)
4343

4444
### Remarks
4545

46-
CE ATL implementation of ActiveX event sinks only supports return values of type HRESULT or void from your event handler methods; any other return value is unsupported and its behavior is undefined.
46+
CE ATL implementation of ActiveX event sinks only supports return values of type HRESULT or void from your event handler methods. Any other return value is unsupported and its behavior is undefined.
4747

4848
## <a name="end_sink_map"></a> END_SINK_MAP
4949

@@ -59,7 +59,7 @@ END_SINK_MAP()
5959

6060
### Remarks
6161

62-
CE ATL implementation of ActiveX event sinks only supports return values of type HRESULT or void from your event handler methods; any other return value is unsupported and its behavior is undefined.
62+
CE ATL implementation of ActiveX event sinks only supports return values of type HRESULT or void from your event handler methods. Any other return value is unsupported and its behavior is undefined.
6363

6464
## <a name="sink_entry"></a> SINK_ENTRY
6565

@@ -86,7 +86,7 @@ SINK_ENTRY( id, dispid, fn )
8686

8787
### Remarks
8888

89-
CE ATL implementation of ActiveX event sinks only supports return values of type HRESULT or void from your event handler methods; any other return value is unsupported and its behavior is undefined.
89+
CE ATL implementation of ActiveX event sinks only supports return values of type HRESULT or void from your event handler methods. Any other return value is unsupported and its behavior is undefined.
9090

9191
## <a name="sink_entry_ex"></a> SINK_ENTRY_EX and SINK_ENTRY_EX_P
9292

@@ -120,7 +120,7 @@ SINK_ENTRY_EX_P( id, piid, dispid, fn ) // (Visual Studio 2017)
120120

121121
### Remarks
122122

123-
CE ATL implementation of ActiveX event sinks only supports return values of type HRESULT or void from your event handler methods; any other return value is unsupported and its behavior is undefined.
123+
CE ATL implementation of ActiveX event sinks only supports return values of type HRESULT or void from your event handler methods. Any other return value is unsupported and its behavior is undefined.
124124

125125
## <a name="sink_entry_info"></a> SINK_ENTRY_INFO and SINK_ENTRY_INFO_P
126126

@@ -153,7 +153,7 @@ SINK_ENTRY_INFO_P( id, piid, dispid, fn, info ) // (Visual Studio 2017)
153153

154154
### Remarks
155155

156-
The first four macro parameters are the same as those for the [SINK_ENTRY_EX](#sink_entry_ex) macro. The final parameter provides type information for the event. CE ATL implementation of ActiveX event sinks only supports return values of type HRESULT or void from your event handler methods; any other return value is unsupported and its behavior is undefined.
156+
The first four macro parameters are the same as the ones for the [SINK_ENTRY_EX](#sink_entry_ex) macro. The final parameter provides type information for the event. CE ATL implementation of ActiveX event sinks only supports return values of type HRESULT or void from your event handler methods. Any other return value is unsupported and its behavior is undefined.
157157

158158
## See also
159159

‎docs/atl/reference/service-map-macros.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -115,31 +115,31 @@ STDMETHOD(QueryService)(
115115

116116
### Return Value
117117

118-
The returned HRESULT value is one of the following:
118+
The returned HRESULT is one of the following values:
119119

120120
|Return value|Meaning|
121121
|------------------|-------------|
122122
|S_OK|The service was successfully created or retrieved.|
123123
|E_INVALIDARG|One or more of the arguments is invalid.|
124124
|E_OUTOFMEMORY|Memory is insufficient to create the service.|
125125
|E_UNEXPECTED|An unknown error occurred.|
126-
|E_NOINTERFACE|The requested interface is not part of this service, or the service is unknown.|
126+
|E_NOINTERFACE|The requested interface isn't part of this service, or the service is unknown.|
127127

128128
### Remarks
129129

130-
`QueryService` returns an indirect pointer to the requested interface in the specified service. The caller is responsible for releasing this pointer when it is no longer required.
130+
`QueryService` returns an indirect pointer to the requested interface in the specified service. The caller is responsible for releasing this pointer when it's no longer required.
131131

132132
When you call `QueryService`, you pass both a service identifier (*guidService*) and an interface identifier (*riid*). The *guidService* specifies the service to which you want access, and the *riid* identifies an interface that is part of the service. In return, you receive an indirect pointer to the interface.
133133

134-
The object that implements the interface might also implement interfaces that are part of other services. Consider the following:
134+
The object that implements the interface might also implement interfaces that are part of other services. Consider the following possibilities:
135135

136136
- Some of these interfaces might be optional. Not all interfaces defined in the service description are necessarily present on every implementation of the service or on every returned object.
137137

138-
- Unlike calls to `QueryInterface`, passing a different service identifier does not necessarily mean that a different Component Object Model (COM) object is returned.
138+
- Unlike calls to `QueryInterface`, passing a different service identifier doesn't necessarily mean that a different Component Object Model (COM) object is returned.
139139

140-
- The returned object might have additional interfaces that are not part of the definition of the service.
140+
- The returned object might have other interfaces that aren't part of the definition of the service.
141141

142-
Two different services, such as SID_SMyService and SID_SYourService, can both specify the use of the same interface, even though the implementation of the interface might have nothing in common between the two services. This works, because a call to `QueryService` (SID_SMyService, IID_IDispatch) can return a different object than `QueryService` (SID_SYourService, IID_IDispatch). Object identity is not assumed when you specify a different service identifier.
142+
Two different services, such as SID_SMyService and SID_SYourService, can both specify the use of the same interface, even though the implementation of the interface might have nothing in common between the two services. This approach works, because a call to `QueryService` (SID_SMyService, IID_IDispatch) can return a different object than `QueryService` (SID_SYourService, IID_IDispatch). Object identity isn't assumed when you specify a different service identifier.
143143

144144
## See also
145145

0 commit comments

Comments
 (0)