Merge pull request MicrosoftDocs#1040 from msebolt/format-atl-reference-pr8

format atl reference pr8

Author: TrishaMc

docs/atl/reference/object-status-macros.md

@@ -16,7 +16,7 @@ This macro sets flags belonging to ActiveX controls.
 
 |||  
 |-|-|  
-|[DECLARE_OLEMISC_STATUS](#declare_olemisc_status)|Used in ATL ActiveX controls to set the **OLEMISC** flags.|  
+|[DECLARE_OLEMISC_STATUS](#declare_olemisc_status)|Used in ATL ActiveX controls to set the OLEMISC flags.|  
 
 ## Requirements  
  **Header:** atlcom.h  

docs/atl/reference/options-atl-active-server-page-component-wizard.md

@@ -24,7 +24,7 @@ Use this page of the ATL Active Server Page Component Wizard to design for incre
 
 |Option|Description|  
 |------------|-----------------|  
-|`Single`|Specifies that the object uses the single threading model. In the single threading model, an object always runs in the primary COM thread. See [Single-Threaded Apartments](http://msdn.microsoft.com/library/windows/desktop/ms680112) and [InprocServer32](http://msdn.microsoft.com/library/windows/desktop/ms682390) for more information.|  
+|**Single**|Specifies that the object uses the single threading model. In the single threading model, an object always runs in the primary COM thread. See [Single-Threaded Apartments](http://msdn.microsoft.com/library/windows/desktop/ms680112) and [InprocServer32](http://msdn.microsoft.com/library/windows/desktop/ms682390) for more information.|  
 |**Apartment**|Specifies that the object uses apartment threading. Equivalent to single thread apartment. Each object of an apartment-threaded component is assigned an apartment for its thread, for the life of the object; however, multiple threads can be used for multiple objects. Each apartment is tied to a specific thread and has a Windows message pump (default).<br /><br /> See [Single-Threaded Apartments](http://msdn.microsoft.com/library/windows/desktop/ms680112) for more information.|  
 |**Both**|Specifies that the object can use either apartment or free threading, depending from which kind of a thread it is created.|  
 |**Free**|Specifies that the object uses free threading. Free threading is equivalent to a multithread apartment model. See [Multithreaded Apartments](http://msdn.microsoft.com/library/windows/desktop/ms693421) for more information.|  
@@ -44,7 +44,7 @@ Use this page of the ATL Active Server Page Component Wizard to design for incre
 
 |Option|Description|  
 |------------|-----------------|  
-|**ISupportErrorInfo**|Creates support for the [ISupportErrorInfo](../../atl/reference/isupporterrorinfoimpl-class.md) interface so the object can return error information to the client.|  
+|`ISupportErrorInfo`|Creates support for the [ISupportErrorInfo](../../atl/reference/isupporterrorinfoimpl-class.md) interface so the object can return error information to the client.|  
 |**Connection points**|Enables connection points for your object by making your object's class derive from [IConnectionPointContainerImpl](../../atl/reference/iconnectionpointcontainerimpl-class.md).|  
 |**Free-threaded marshaler**|Creates a free-threaded marshaler object to marshal interface pointers efficiently between threads in the same process. Available to object specifying either **Both** or **Free** as the threading model.|  
 

docs/atl/reference/options-atl-control-wizard.md

@@ -69,7 +69,7 @@ Insert "Search Results" summary here.
 
      If you select **Custom**, then you can specify that the control is **Automation compatible**. If you select **Automation compatible**, then the wizard adds the [oleautomation](../../windows/oleautomation.md) attribute to the interface in the IDL, and the interface can be marshaled by the universal marshaler in oleaut32.dll. See [Marshaling Details](http://msdn.microsoft.com/library/windows/desktop/ms692621) in the Windows SDK for more information.  
 
-     Additionally, if you select **Automation compatible**, then all parameters for all methods in the control must be **VARIANT** compatible.  
+     Additionally, if you select **Automation compatible**, then all parameters for all methods in the control must be VARIANT compatible.  
 
  **Support**  
  Sets additional miscellaneous support for the control.  

docs/atl/reference/options-atl-property-page-wizard.md

@@ -22,7 +22,7 @@ Use this page of the wizard to define the threading model and aggregation level
 
 |Option|Description|  
 |------------|-----------------|  
-|`Single`|The property page runs only in the primary COM thread.|  
+|**Single**|The property page runs only in the primary COM thread.|  
 |**Apartment**|The property page can be created in any single thread apartment. The default.|  
 
  **Aggregation**  

docs/atl/reference/options-atl-simple-object-wizard.md

@@ -24,7 +24,7 @@ Use this page of the ATL Simple Object Wizard to design for increased efficiency
 
 |Option|Description|  
 |------------|-----------------|  
-|`Single`|Specifies that the object always runs in the primary COM thread. See [Single-Threaded Apartments](http://msdn.microsoft.com/library/windows/desktop/ms680112) and [InprocServer32](http://msdn.microsoft.com/library/windows/desktop/ms682390) for more information.|  
+|**Single**|Specifies that the object always runs in the primary COM thread. See [Single-Threaded Apartments](http://msdn.microsoft.com/library/windows/desktop/ms680112) and [InprocServer32](http://msdn.microsoft.com/library/windows/desktop/ms682390) for more information.|  
 |**Apartment**|Specifies that the object uses apartment threading. Equivalent to single thread apartment. Each object of an apartment-threaded component is assigned an apartment for its thread, for the life of the object; however, multiple threads can be used for multiple objects. Each apartment is tied to a specific thread and has a Windows message pump (default).<br /><br /> See [Single-Threaded Apartments](http://msdn.microsoft.com/library/windows/desktop/ms680112) for more information.|  
 |**Both**|Specifies that the object can use either apartment or free threading, depending from which kind of a thread it is created.|  
 |**Free**|Specifies that the object uses free threading. Free threading is equivalent to a multithread apartment model. See [Multithreaded Apartments](http://msdn.microsoft.com/library/windows/desktop/ms693421) for more information.|  
@@ -52,10 +52,10 @@ Use this page of the ATL Simple Object Wizard to design for increased efficiency
 
 |Option|Description|  
 |------------|-----------------|  
-|**ISupportErrorInfo**|Creates support for the [ISupportErrorInfo](../../atl/reference/isupporterrorinfoimpl-class.md) interface so the object can return error information to the client.|  
+|`ISupportErrorInfo`|Creates support for the [ISupportErrorInfo](../../atl/reference/isupporterrorinfoimpl-class.md) interface so the object can return error information to the client.|  
 |**Connection points**|Enables connection points for your object by making your object's class derive from [IConnectionPointContainerImpl](../../atl/reference/iconnectionpointcontainerimpl-class.md).|  
 |**Free-threaded marshaler**|Creates a free-threaded marshaler object to marshal interface pointers efficiently between threads in the same process. Available to object specifying **Both** as the threading model.|  
-|**IObjectWithSite (IE object support)**|Implements [IObjectWithSiteImpl](../../atl/reference/iobjectwithsiteimpl-class.md), which provides a simple way to support communication between an object and its site in a container.|  
+|`IObjectWithSite` **(IE object support)**|Implements [IObjectWithSiteImpl](../../atl/reference/iobjectwithsiteimpl-class.md), which provides a simple way to support communication between an object and its site in a container.|  
 
 ## See Also  
  [ATL Simple Object Wizard](../../atl/reference/atl-simple-object-wizard.md)   

docs/atl/reference/pixel-himetric-conversion-global-functions.md

@@ -33,10 +33,10 @@ extern void AtlHiMetricToPixel(
 ```  
 
 ### Parameters  
- `lpSizeInHiMetric`  
+ *lpSizeInHiMetric*  
  [in] Pointer to the size of the object in HIMETRIC units.  
 
- `lpSizeInPix`  
+ *lpSizeInPix*  
  [out] Pointer to where the object's size in pixels is to be returned.  
 
 ### Example  
@@ -55,10 +55,10 @@ extern void AtlPixelToHiMetric(
 ```  
 
 ### Parameters  
- `lpSizeInPix`  
+ *lpSizeInPix*  
  [in] Pointer to the object's size in pixels.  
 
- `lpSizeInHiMetric`  
+ *lpSizeInHiMetric*  
  [out] Pointer to where the object's size in HIMETRIC units is to be returned.  
 
 ### Example  

docs/atl/reference/property-map-macros.md

@@ -35,15 +35,15 @@ BEGIN_PROP_MAP(theClass)
 ```  
 
 ### Parameters  
- `theClass`  
+ *theClass*  
  [in] Specifies the class containing the property map.  
 
 ### Remarks  
  The property map stores property descriptions, property DISPIDs, property page CLSIDs, and `IDispatch` IIDs. Classes [IPerPropertyBrowsingImpl](../../atl/reference/iperpropertybrowsingimpl-class.md), [IPersistPropertyBagImpl](../../atl/reference/ipersistpropertybagimpl-class.md), [IPersistStreamInitImpl](../../atl/reference/ipersiststreaminitimpl-class.md), and [ISpecifyPropertyPagesImpl](../../atl/reference/ispecifypropertypagesimpl-class.md) use the property map to retrieve and set this information.  
 
- When you create an object with the ATL Project Wizard, the wizard will create an empty property map by specifying `BEGIN_PROP_MAP` followed by [END_PROP_MAP](#end_prop_map).  
+ When you create an object with the ATL Project Wizard, the wizard will create an empty property map by specifying BEGIN_PROP_MAP followed by [END_PROP_MAP](#end_prop_map).  
 
- `BEGIN_PROP_MAP` does not save out the extent (that is, the dimensions) of a property map, because an object using a property map may not have a user interface, so it would have no extent. If the object is an ActiveX control with a user interface, it has an extent. In this case, you must specify [PROP_DATA_ENTRY](#prop_data_entry) in your property map to supply the extent.  
+ BEGIN_PROP_MAP does not save out the extent (that is, the dimensions) of a property map, because an object using a property map may not have a user interface, so it would have no extent. If the object is an ActiveX control with a user interface, it has an extent. In this case, you must specify [PROP_DATA_ENTRY](#prop_data_entry) in your property map to supply the extent.  
 
 ### Example  
  [!code-cpp[NVC_ATL_Windowing#103](../../atl/codesnippet/cpp/property-map-macros_1.h)]  
@@ -56,10 +56,10 @@ PROP_DATA_ENTRY( szDesc, member, vt)
 ```    
 
 ### Parameters  
- `szDesc`  
+ *szDesc*  
  [in] The property description.  
 
- `member`  
+ *member*  
  [in] The data member containing the extent; for example, `m_sizeExtent`.  
 
  *vt*  
@@ -71,7 +71,7 @@ PROP_DATA_ENTRY( szDesc, member, vt)
  When you create an ActiveX control, the wizard inserts this macro after the property map macro [BEGIN_PROP_MAP](#begin_prop_map) and before the property map macro [END_PROP_MAP](#end_prop_map).  
 
 ### Example  
- In the following example, the extent of the object ( `m_sizeExtent`) is being persisted.  
+ In the following example, the extent of the object (`m_sizeExtent`) is being persisted.  
 
  [!code-cpp[NVC_ATL_Windowing#131](../../atl/codesnippet/cpp/property-map-macros_2.h)]  
 
@@ -85,20 +85,20 @@ PROP_ENTRY_TYPE( szDesc, dispid, clsid, vt)
 ```  
 
 ### Parameters  
- `szDesc`  
+ *szDesc*  
  [in] The property description.  
 
- `dispid`  
+ *dispid*  
  [in] The property's DISPID.  
 
- `clsid`  
- [in] The CLSID of the associated property page. Use the special value `CLSID_NULL` for a property that does not have an associated property page.  
+ *clsid*  
+ [in] The CLSID of the associated property page. Use the special value CLSID_NULL for a property that does not have an associated property page.  
 
- `vt`  
+ *vt*  
  [in] The property's type.  
 
 ### Remarks  
- The `PROP_ENTRY` macro was insecure and deprecated. It has been replaced with `PROP_ENTRY_TYPE`.  
+ The PROP_ENTRY macro was insecure and deprecated. It has been replaced with PROP_ENTRY_TYPE.  
 
  The [BEGIN_PROP_MAP](#begin_prop_map) macro marks the beginning of the property map; the [END_PROP_MAP](#end_prop_map) macro marks the end.  
 
@@ -113,23 +113,23 @@ PROP_ENTRY_TYPE_EX( szDesc, dispid, clsid, iidDispatch, vt)
 ```    
 
 ### Parameters  
- `szDesc`  
+ *szDesc*  
  [in] The property description.  
 
- `dispid`  
+ *dispid*  
  [in] The property's DISPID.  
 
- `clsid`  
- [in] The CLSID of the associated property page. Use the special value `CLSID_NULL` for a property that does not have an associated property page.  
+ *clsid*  
+ [in] The CLSID of the associated property page. Use the special value CLSID_NULL for a property that does not have an associated property page.  
 
- `iidDispatch`  
+ *iidDispatch*  
  [in] The IID of the dual interface defining the property.  
 
- `vt`  
+ *vt*  
  [in] The property's type.  
 
 ### Remarks  
- The `PROP_ENTRY_EX` macro was insecure and deprecated. It has been replaced with `PROP_ENTRY_TYPE_EX`.  
+ The PROP_ENTRY_EX macro was insecure and deprecated. It has been replaced with PROP_ENTRY_TYPE_EX.  
 
  The [BEGIN_PROP_MAP](#begin_prop_map) macro marks the beginning of the property map; the [END_PROP_MAP](#end_prop_map) macro marks the end.  
 
@@ -146,14 +146,14 @@ PROP_PAGE(clsid)
 ```  
 
 ### Parameters  
- `clsid`  
+ *clsid*  
  [in] The CLSID of a property page.  
 
 ### Remarks  
- `PROP_PAGE` is similar to [PROP_ENTRY_TYPE](#prop_entry_type), but does not require a property description or DISPID.  
+ PROP_PAGE is similar to [PROP_ENTRY_TYPE](#prop_entry_type), but does not require a property description or DISPID.  
 
 > [!NOTE]
->  If you have already entered a CLSID with `PROP_ENTRY_TYPE` or [PROP_ENTRY_TYPE_EX](#prop_entry_type_ex), you do not need to make an additional entry with `PROP_PAGE`.  
+>  If you have already entered a CLSID with PROP_ENTRY_TYPE or [PROP_ENTRY_TYPE_EX](#prop_entry_type_ex), you do not need to make an additional entry with PROP_PAGE.  
   
  The [BEGIN_PROP_MAP](#begin_prop_map) macro marks the beginning of the property map; the [END_PROP_MAP](#end_prop_map) macro marks the end.  
 
@@ -168,7 +168,7 @@ END_PROP_MAP()
 ```  
 
 ### Remarks  
- When you create an object with the ATL Project Wizard, the wizard will create an empty property map by specifying [BEGIN_PROP_MAP](#begin_prop_map) followed by `END_PROP_MAP`.  
+ When you create an object with the ATL Project Wizard, the wizard will create an empty property map by specifying [BEGIN_PROP_MAP](#begin_prop_map) followed by END_PROP_MAP.  
 
 ### Example  
  See the example for [BEGIN_PROP_MAP](#begin_prop_map).