Add missing space before links

docs/debugger/debugging-preparation-visual-cpp-project-types.md

@@ -80,12 +80,12 @@ This section describes how to debug the basic project types created by the Visua
 
 6. Open the **Linker** node, and select **Debugging**. In the first **Generate** row, select **Yes (/DEBUG)** from the drop-down list. Always set this when you are debugging.
 
-   For more information, see[Project Settings for a C++ Debug Configuration](../debugger/project-settings-for-a-cpp-debug-configuration.md).
+   For more information, see [Project Settings for a C++ Debug Configuration](../debugger/project-settings-for-a-cpp-debug-configuration.md).
 
    [In this topic](../debugger/debugging-preparation-visual-cpp-project-types.md#BKMK_In_this_topic)
 
 ## Related content
 - [First look at the debugger](../debugger/debugger-feature-tour.md)
 - [Project Settings for a C++ Debug Configuration](../debugger/project-settings-for-a-cpp-debug-configuration.md)
 - [Attaching to a Running Program or Multiple Programs](../debugger/attach-to-running-processes-with-the-visual-studio-debugger.md)
-- [Debug and Release Configurations](../debugger/how-to-set-debug-and-release-configurations.md)
+- [Debug and Release Configurations](../debugger/how-to-set-debug-and-release-configurations.md)

docs/extensibility/debugger/control-events.md

@@ -19,7 +19,7 @@ You must send events during the controlled execution of your program. All of the
 
 - Sending the [IDebugEngineCreateEvent2](../../extensibility/debugger/reference/idebugenginecreateevent2.md) interface when the debug engine (DE) is initialized requires you to implement the [IDebugEngineCreateEvent2::GetEngine](../../extensibility/debugger/reference/idebugenginecreateevent2-getengine.md) method.
 
-- Execution control requires implementation of such control events as the [IDebugBreakEvent2](../../extensibility/debugger/reference/idebugbreakevent2.md) and[IDebugStepCompleteEvent2](../../extensibility/debugger/reference/idebugstepcompleteevent2.md) interfaces. **IDebugBreakEvent2** is required only for asynchronous breaks.
+- Execution control requires implementation of such control events as the [IDebugBreakEvent2](../../extensibility/debugger/reference/idebugbreakevent2.md) and [IDebugStepCompleteEvent2](../../extensibility/debugger/reference/idebugstepcompleteevent2.md) interfaces. **IDebugBreakEvent2** is required only for asynchronous breaks.
 
 - Stepping into functions requires implementation of the [IDebugStepCompleteEvent2](../../extensibility/debugger/reference/idebugstepcompleteevent2.md) interface and its methods.
 

docs/extensibility/debugger/implementing-and-registering-a-port-supplier.md

@@ -16,7 +16,7 @@ ms.subservice: debug-diagnostics
 The role of a port supplier is to track and supply ports, which in turn manage processes. When a port needs to be created, the port supplier is instantiated using CoCreate with the port supplier's GUID (the session debug manager [SDM] will use the port supplier that the user selected or the port supplier specified by the project system). The SDM then calls [CanAddPort](../../extensibility/debugger/reference/idebugportsupplier2-canaddport.md) to see if any ports can be added. If a port can be added, a new port is requested by calling [AddPort](../../extensibility/debugger/reference/idebugportsupplier2-addport.md) and passing it an [IDebugPortRequest2](../../extensibility/debugger/reference/idebugportrequest2.md) that describes the port. `AddPort` returns a new port represented by an [IDebugPort2](../../extensibility/debugger/reference/idebugport2.md) interface.
 
 ## Discussion
- A port is created by a port supplier, which is associated with a machine or debug server. A server enumerates its port suppliers through the[EnumPortSuppliers](../../extensibility/debugger/reference/idebugcoreserver2-enumportsuppliers.md) method, and a port supplier enumerates its ports through the [EnumPorts](../../extensibility/debugger/reference/idebugportsupplier2-enumports.md) method.
+ A port is created by a port supplier, which is associated with a machine or debug server. A server enumerates its port suppliers through the [EnumPortSuppliers](../../extensibility/debugger/reference/idebugcoreserver2-enumportsuppliers.md) method, and a port supplier enumerates its ports through the [EnumPorts](../../extensibility/debugger/reference/idebugportsupplier2-enumports.md) method.
 
  In addition to the typical COM registration, a port supplier must register itself with Visual Studio by placing its CLSID and name in specific registry locations. A Debugging SDK helper function called `SetMetric` handles this chore: it is called once for each item to be registered, thus:
 

docs/extensibility/debugger/reference/bp-passcount.md

@@ -1,6 +1,6 @@
 ---
-description: "Describes the count and conditions upon which a conditional breakpoint is fired."
 title: BP_PASSCOUNT
+description: "Describes the count and conditions upon which a conditional breakpoint is fired."
 ms.date: 11/04/2016
 ms.topic: reference
 f1_keywords:
@@ -47,7 +47,7 @@ A value from the [BP_PASSCOUNT_STYLE](../../../extensibility/debugger/reference/
 ## Remarks
 This structure is a member of the [BP_REQUEST_INFO](../../../extensibility/debugger/reference/bp-request-info.md) structure.
 
-This structure is also passed as a parameter to the[SetPassCount](../../../extensibility/debugger/reference/idebugboundbreakpoint2-setpasscount.md) and[SetPassCount](../../../extensibility/debugger/reference/idebugpendingbreakpoint2-setpasscount.md) methods.
+This structure is also passed as a parameter to the [SetPassCount](../../../extensibility/debugger/reference/idebugboundbreakpoint2-setpasscount.md) and [SetPassCount](../../../extensibility/debugger/reference/idebugpendingbreakpoint2-setpasscount.md) methods.
 
 ## Requirements
 Header: msdbg.h

docs/extensibility/debugger/reference/debug-address-union.md

@@ -1,6 +1,6 @@
 ---
-description: "Describes different kinds of addresses."
 title: DEBUG_ADDRESS_UNION
+description: "Describes different kinds of addresses."
 ms.date: 11/04/2016
 ms.topic: reference
 f1_keywords:
@@ -56,28 +56,28 @@ A value from the [ADDRESS_KIND](../../../extensibility/debugger/reference/addres
 [C++ only] Contains the [NATIVE_ADDRESS](../../../extensibility/debugger/reference/native-address.md) structure if `dwKind` = ADDRESS_KIND_NATIVE.
 
 `addr.addrThisRel`\
-[C++ only] Contains the[UNMANAGED_ADDRESS_THIS_RELATIVE](../../../extensibility/debugger/reference/unmanaged-address-this-relative.md) structure if `dwKind` = ADDRESS_KIND_UNMANAGED_THIS_RELATIVE.
+[C++ only] Contains the [UNMANAGED_ADDRESS_THIS_RELATIVE](../../../extensibility/debugger/reference/unmanaged-address-this-relative.md) structure if `dwKind` = ADDRESS_KIND_UNMANAGED_THIS_RELATIVE.
 
 `addr.addUPhysical`\
-[C++ only] Contains the[UNMANAGED_ADDRESS_PHYSICAL](../../../extensibility/debugger/reference/unmanaged-address-physical.md) structure if `dwKind` = ADDRESS_KIND_UNMANAGED_PHYSICAL.
+[C++ only] Contains the [UNMANAGED_ADDRESS_PHYSICAL](../../../extensibility/debugger/reference/unmanaged-address-physical.md) structure if `dwKind` = ADDRESS_KIND_UNMANAGED_PHYSICAL.
 
 `addr.addrMethod`\
-[C++ only] Contains the[METADATA_ADDRESS_METHOD](../../../extensibility/debugger/reference/metadata-address-method.md) structure if `dwKind` = ADDRESS_KIND_METHOD.
+[C++ only] Contains the [METADATA_ADDRESS_METHOD](../../../extensibility/debugger/reference/metadata-address-method.md) structure if `dwKind` = ADDRESS_KIND_METHOD.
 
 `addr.addrField`\
-[C++ only] Contains the[METADATA_ADDRESS_FIELD](../../../extensibility/debugger/reference/metadata-address-field.md) structure if `dwKind` = ADDRESS_KIND_FIELD.
+[C++ only] Contains the [METADATA_ADDRESS_FIELD](../../../extensibility/debugger/reference/metadata-address-field.md) structure if `dwKind` = ADDRESS_KIND_FIELD.
 
 `addr.addrLocal`\
-[C++ only] Contains the[METADATA_ADDRESS_LOCAL](../../../extensibility/debugger/reference/metadata-address-local.md) structure if `dwKind` = ADDRESS_KIND_LOCAL.
+[C++ only] Contains the [METADATA_ADDRESS_LOCAL](../../../extensibility/debugger/reference/metadata-address-local.md) structure if `dwKind` = ADDRESS_KIND_LOCAL.
 
 `addr.addrParam`\
-[C++ only] Contains the[METADATA_ADDRESS_PARAM](../../../extensibility/debugger/reference/metadata-address-param.md) structure if `dwKind` = ADDRESS_KIND_PARAM.
+[C++ only] Contains the [METADATA_ADDRESS_PARAM](../../../extensibility/debugger/reference/metadata-address-param.md) structure if `dwKind` = ADDRESS_KIND_PARAM.
 
 `addr.addrArrayElem`\
-[C++ only] Contains the[METADATA_ADDRESS_ARRAYELEM](../../../extensibility/debugger/reference/metadata-address-arrayelem.md) structure if `dwKind` = ADDRESS_KIND_ARRAYELEM.
+[C++ only] Contains the [METADATA_ADDRESS_ARRAYELEM](../../../extensibility/debugger/reference/metadata-address-arrayelem.md) structure if `dwKind` = ADDRESS_KIND_ARRAYELEM.
 
 `addr.addrRetVal`\
-[C++ only] Contains the[METADATA_ADDRESS_RETVAL](../../../extensibility/debugger/reference/metadata-address-retval.md) structure if `dwKind` = ADDRESS_KIND_RETVAL.
+[C++ only] Contains the [METADATA_ADDRESS_RETVAL](../../../extensibility/debugger/reference/metadata-address-retval.md) structure if `dwKind` = ADDRESS_KIND_RETVAL.
 
 `addr.unused`\
 [C++ only] padding.

docs/extensibility/debugger/reference/idebugbreakpointrequest2-getlocationtype.md

@@ -1,6 +1,6 @@
 ---
-description: "Gets the breakpoint location type of this breakpoint request."
 title: IDebugBreakpointRequest2::GetLocationType
+description: "Gets the breakpoint location type of this breakpoint request."
 ms.date: 11/04/2016
 ms.topic: reference
 f1_keywords:
@@ -43,7 +43,7 @@ HRESULT GetLocationType(
 If successful, returns `S_OK`; otherwise, returns an error code. Returns `E_FAIL` if the `bpLocation` field in the associated [BP_REQUEST_INFO](../../../extensibility/debugger/reference/bp-request-info.md) structure is not valid.
 
 ## Example
-The following example shows how to implement this method for a simple `CDebugBreakpointRequest` object that exposes the[IDebugBreakpointRequest2](../../../extensibility/debugger/reference/idebugbreakpointrequest2.md) interface.
+The following example shows how to implement this method for a simple `CDebugBreakpointRequest` object that exposes the [IDebugBreakpointRequest2](../../../extensibility/debugger/reference/idebugbreakpointrequest2.md) interface.
 
 ```
 HRESULT CDebugBreakpointRequest::GetLocationType(BP_LOCATION_TYPE* pBPLocationType)

docs/extensibility/internals/services-provided-source-control-vspackage.md

@@ -13,7 +13,7 @@ ms.subservice: extensibility-integration
 ---
 # Services Provided (Source Control VSPackage)
 
-Services are the primary mechanism through which functionality is shared among VSPackages and between the Visual Studio integrated development environment (IDE) and its installed VSPackages. For detailed description of services and their importance in the Visual Studio IDE, see[Using and Providing Services](../../extensibility/using-and-providing-services.md).
+Services are the primary mechanism through which functionality is shared among VSPackages and between the Visual Studio integrated development environment (IDE) and its installed VSPackages. For detailed description of services and their importance in the Visual Studio IDE, see [Using and Providing Services](../../extensibility/using-and-providing-services.md).
 
 ## The Source Control Service
  Visual Studio provides two layers of services, IDE-level services and package-level services. The Visual Studio IDE natively provides IDE-level services. The source control package consumes some of these services. The source control package as a VSPackage shares its source control functionality by providing a private source control service of its own. The source control package encapsulates the set of source control-related interfaces implemented by it in the form of a contract that can be used by the Visual Studio IDE.

docs/extensibility/walkthrough-creating-a-view-adornment-commands-and-settings-column-guides.md

@@ -20,7 +20,7 @@ In this walkthrough, you:
 - Place the commands on the Edit menu and text document context menus
 - Add support for invoking the commands from the Visual Studio Command Window
 
-  You can try out a version of the column guides feature with this Visual Studio Gallery[extension](https://marketplace.visualstudio.com/items?itemName=PaulHarrington.EditorGuidelines).
+  You can try out a version of the column guides feature with this Visual Studio Gallery [extension](https://marketplace.visualstudio.com/items?itemName=PaulHarrington.EditorGuidelines).
 
   > [!NOTE]
   > In this walkthrough, you paste a great amount of code into a few files generated by Visual Studio extension templates. But, soon this walkthrough will refer to a completed solution on GitHub with other extension examples. The completed code is slightly different in that it has real command icons instead of using generictemplate icons.
@@ -1328,7 +1328,7 @@ If you want to try different command placements, change names, change icons, and
 ## Finished code project
 There will soon be a GitHub project of Visual Studio Extensibility samples, and the completed project will be there. This article will be updated to point there when that happens. The completed sample project may have different guids and will have a different bitmaps strip for the command icons.
 
-You can try out a version of the column guides feature with this Visual Studio Gallery[extension](https://marketplace.visualstudio.com/items?itemName=PaulHarrington.EditorGuidelines).
+You can try out a version of the column guides feature with this Visual Studio Gallery [extension](https://marketplace.visualstudio.com/items?itemName=PaulHarrington.EditorGuidelines).
 
 ## Related content
 - [Inside the editor](../extensibility/inside-the-editor.md)