Merge pull request MicrosoftDocs#1989 from nschonni/fix--MD009/no-trailing-spaces

fix: MD009/no-trailing-spaces

Author: Colin Robertson

docs/assembler/masm/invoke.md

@@ -7,7 +7,7 @@ ms.assetid: 12d9bb40-33b9-411e-b801-45a1d675967e
 ---
 # INVOKE
 
-(32-bit MASM only.) Calls the procedure at the address given by *expression*, passing the arguments on the stack or in registers according to the standard calling conventions of the language type.     
+(32-bit MASM only.) Calls the procedure at the address given by *expression*, passing the arguments on the stack or in registers according to the standard calling conventions of the language type.
 
 ## Syntax
 

docs/assembler/masm/struct-masm.md

@@ -17,7 +17,7 @@ Declares a structure type having the specified *field-declarations*. Each field
 
 ## Remarks
 
-The *name* argument must be the same in the opening and closing statement. 
+The *name* argument must be the same in the opening and closing statement.
 
 ## See also
 

docs/atl/adding-a-property-page-atl-tutorial-part-6.md

@@ -6,7 +6,7 @@ ms.assetid: df80d255-e7ea-49d9-b940-3f012e90cf9b
 ---
 # Adding a Property Page (ATL Tutorial, Part 6)
 
-> [!NOTE] 
+> [!NOTE]
 > The ATL OLE DB Provider wizard is not available in Visual Studio 2019 and later.
 
 Property pages are implemented as separate COM objects, which allow them to be shared if required. In this step, you will do the following tasks to add a property page to the control:

docs/atl/creating-the-project-atl-tutorial-part-1.md

@@ -39,7 +39,7 @@ This tutorial walks you step-by-step through a non-attributed ATL project that c
 
     The location for the source code will usually default to \Users\\\<username>\source\repos, and a new folder will be created automatically.
 
-1. In Visual Studio 2019, accept the default values and click **OK**. 
+1. In Visual Studio 2019, accept the default values and click **OK**.
    In Visual Studio 2017, click **OK** to open the **ATL Project** wizard. Click **Application Settings** to see the options available. Because this project creates a control, and a control must be an in-process server, leave the **Application type** as a DLL. Click **OK**.
 
 Visual Studio will create the project by generating several files. You can view these files in **Solution Explorer** by expanding the `Polygon` object. The files are listed below.

docs/atl/reference/adding-an-atl-property-page.md

@@ -6,7 +6,7 @@ ms.assetid: ddf92b49-42a2-46d2-b6b8-d37baedebeca
 ---
 # Adding an ATL Property Page
 
-> [!NOTE] 
+> [!NOTE]
 > The ATL Property Page wizard is not available in Visual Studio 2019 and later.
 
 To add an Active Template Library (ATL) property page to your project, your project must have been created as an ATL application or as an MFC application that contains ATL support. You can use the [ATL Project Wizard](../../atl/reference/atl-project-wizard.md) to create an ATL application or [add an ATL object to your MFC application](../../mfc/reference/adding-atl-support-to-your-mfc-project.md) to implement ATL support for an MFC application.

docs/atl/reference/adding-objects-and-controls-to-an-atl-project.md

@@ -7,7 +7,7 @@ ms.assetid: c0adcbd0-07fe-4c55-a8fd-8c2c65ecdaad
 ---
 # Adding Objects and Controls to an ATL Project
 
-> [!NOTE] 
+> [!NOTE]
 > The ATL COM+ 1.0 Component Wizard, ATL OLE DB Consumer wizard, and ATL Active Server Page Component wizard are not available in Visual Studio 2019 and later.
 
 You can use one of the ATL code wizards to add an object or a control to your ATL- or MFC-based projects. For each COM object or control you add, the wizard generates .cpp and .h files, as well as an .rgs file for script-based registry support. The following ATL code wizards are available in Visual Studio:

docs/atl/reference/atl-com-plus-1-0-component-wizard.md

@@ -78,7 +78,7 @@ Provides information about the COM functionality for the object.
 - **ProgID**
 
    Sets the name that containers can use instead of the CLSID of the object.
-   
+
 ::: moniker-end
 
 ## See also

docs/atl/reference/cstockpropimpl-class.md

@@ -16,12 +16,12 @@ This class provides methods for supporting stock property values.
 
 ```
 template <
-    class T, 
+    class T,
     class InterfaceName,
     const IID* piid = &_ATL_IIDOF(InterfaceName),
     const GUID* plibid = &CComModule::m_libid,
     WORD wMajor = 1,
-    WORD wMinor = 0, 
+    WORD wMinor = 0,
     class tihclass = CcomTypeInfoHolder>
 class ATL_NO_VTABLE CStockPropImpl :
     public IDispatchImpl<InterfaceName, piid, plibid, wMajor, wMinor, tihclass>

docs/build/adding-references-in-visual-cpp-projects.md

@@ -7,7 +7,7 @@ ms.assetid: 12b8f571-0f21-40b3-9404-5318a57e9cb5
 ---
 # Consuming libraries and components
 
-Often, a C++ project needs to call functions or access data in a binary file such as static library (.lib files), DLL, Windows Runtime component, COM component, or .NET assembly. In these cases, you have to configure the project so that it can find that binary at build time. The specific steps depend on the type of your project, the type of the binary, and whether the binary is being built in the same solution as your project. 
+Often, a C++ project needs to call functions or access data in a binary file such as static library (.lib files), DLL, Windows Runtime component, COM component, or .NET assembly. In these cases, you have to configure the project so that it can find that binary at build time. The specific steps depend on the type of your project, the type of the binary, and whether the binary is being built in the same solution as your project.
 
 ## Consuming libraries downloaded via vcpkg
 
@@ -18,11 +18,11 @@ To consume a library that you have downloaded by using the **vcpkg** package man
 If your static library project is being built in the same solution:
 
 1. #include the header file(s) for the static library using quotation marks. In a typical solution the path will start with `../<library project name>`. IntelliSense will help you find it.
-2. Add a reference to the static library project. Right-click on **References** under the application project node in **Solution Explorer** and choose **Add Reference**. 
+2. Add a reference to the static library project. Right-click on **References** under the application project node in **Solution Explorer** and choose **Add Reference**.
 
 If the static library is not part of the solution:
 
-1. Right-click on the application project node in **Solution Explorer** and then choose **Properties**. 
+1. Right-click on the application project node in **Solution Explorer** and then choose **Properties**.
 2. In the **VC++ Directories** property page, add the path to the directory where the .lib file is located in **Library Paths** and add the path to the library header file(s) in **Include Directories**.  
 3. In the **Linker > Input** property page, add the name of the .lib file to **Additional Dependencies**.
 
@@ -37,11 +37,11 @@ If the DLL is not part of the application solution, you need the DLL file, the h
 
 ## COM objects
 
-If your native C++ application needs to consume a COM object, and that object is *registered*, then all you have to do is call CoCreateInstance and pass in the CLSID of the object. The system will find it in the Windows Registry and load it. A C++/CLI project can consume a COM object in the same way, or by adding a reference to it from the **Add References > COM** list and consuming it through its [Runtime callable wrapper](/dotnet/framework/interop/runtime-callable-wrapper). 
+If your native C++ application needs to consume a COM object, and that object is *registered*, then all you have to do is call CoCreateInstance and pass in the CLSID of the object. The system will find it in the Windows Registry and load it. A C++/CLI project can consume a COM object in the same way, or by adding a reference to it from the **Add References > COM** list and consuming it through its [Runtime callable wrapper](/dotnet/framework/interop/runtime-callable-wrapper).
 
 ## .NET assemblies and Windows Runtime Components
 
-In UWP or C++/CLI projects, you consume .NET assemblies or Windows Runtime Components by adding a *reference* to the assembly or component. Under the **References** node in a UWP or C++/CLI project, you see references to commonly-used components. Right-click on the **References** node in **Solution Explorer** to bring up the **Reference Manager** and browse through additional components that are known to the system. Click the **Browse** button to navigate to any folder where a custom component is located. Because .NET assemblies and Windows Runtime components contain built-in type information, you can view their methods and classes by right-clicking and choosing **View in Object Browser**. 
+In UWP or C++/CLI projects, you consume .NET assemblies or Windows Runtime Components by adding a *reference* to the assembly or component. Under the **References** node in a UWP or C++/CLI project, you see references to commonly-used components. Right-click on the **References** node in **Solution Explorer** to bring up the **Reference Manager** and browse through additional components that are known to the system. Click the **Browse** button to navigate to any folder where a custom component is located. Because .NET assemblies and Windows Runtime components contain built-in type information, you can view their methods and classes by right-clicking and choosing **View in Object Browser**.
 
 ## Reference properties
 

docs/build/clang-support-msbuild.md

@@ -19,7 +19,7 @@ You can use Visual Studio 2019 version 16.2 with Clang to edit, build, and debug
 
 ## Install
 
-For best IDE support in Visual Studio, we recommend using the latest Clang compiler tools for Windows. If you don't already have those, you can install them by opening the Visual Studio Installer and choosing **C++ Clang tools for Windows** under **Desktop development with C++** optional components. If you prefer to use an existing Clang installation on your machine, choose the **C++ Clang-cl for v142 build tools.** optional component. The Microsoft C++ Standard Library currently requires at least Clang 8.0.0; the bundled version of Clang will automatically be updated to stay current with updates in the Microsoft implementation of the Standard Library. 
+For best IDE support in Visual Studio, we recommend using the latest Clang compiler tools for Windows. If you don't already have those, you can install them by opening the Visual Studio Installer and choosing **C++ Clang tools for Windows** under **Desktop development with C++** optional components. If you prefer to use an existing Clang installation on your machine, choose the **C++ Clang-cl for v142 build tools.** optional component. The Microsoft C++ Standard Library currently requires at least Clang 8.0.0; the bundled version of Clang will automatically be updated to stay current with updates in the Microsoft implementation of the Standard Library.
 
 ![Clang component installation](media/clang-install-vs2019.png)
 
@@ -39,8 +39,8 @@ For Linux projects, Visual Studio uses the Clang GCC-compatible frontend. The pr
 
 To configure a Visual Studio Linux project to use Clang:
 
-1. Right-click on the project node in **Solution Explorer** and choose **Properties**. 
-1. Typically, you should first choose **All configurations** at the top of the dialog. 
+1. Right-click on the project node in **Solution Explorer** and choose **Properties**.
+1. Typically, you should first choose **All configurations** at the top of the dialog.
 1. Under **General** > **Platform Toolset**, choose **WSL_Clang_1_0** if you are using Windows Subsystem for Linux, or **Remote_Clang_1_0** if you are using a remote machine or VM.
 1. Press **OK**.