MicrosoftDocs · TylerMSFT · Mar 27, 2020 · Mar 27, 2020
diff --git a/docs/atl/using-replaceable-parameters-the-registrar-s-preprocessor.md b/docs/atl/using-replaceable-parameters-the-registrar-s-preprocessor.md
@@ -35,7 +35,7 @@ During the parsing of the script, the Registrar expands `'%MODULE%, 1'` to `c:\m
 > [!NOTE]
 > When building a project that outputs an executable, ATL automatically adds quotation marks around the path name created at run time with the **%MODULE%** registrar script parameter. If you do not want the path name to include the quotation marks, use the new **%MODULE_RAW%** parameter instead.
 >
->  When building a project that outputs a DLL, ATL will not add quotation marks to the path name if **%MODULE%** or **%MODULE_RAW%** is used.
+> When building a project that outputs a DLL, ATL will not add quotation marks to the path name if **%MODULE%** or **%MODULE_RAW%** is used.
 
 ## See also
 

diff --git a/docs/cpp/namespaces-cpp.md b/docs/cpp/namespaces-cpp.md
@@ -56,7 +56,7 @@ The **using** directive allows all the names in a **namespace** to be used witho
 > [!NOTE]
 > A using directive can be placed at the top of a .cpp file (at file scope), or inside a class or function definition.
 >
->  In general, avoid putting using directives in header files (*.h) because any file that includes that header will bring everything in the namespace into scope, which can cause name hiding and name collision problems that are very difficult to debug. Always use fully qualified names in a header file. If those names get too long, you can use a namespace alias to shorten them. (See below.)
+> In general, avoid putting using directives in header files (*.h) because any file that includes that header will bring everything in the namespace into scope, which can cause name hiding and name collision problems that are very difficult to debug. Always use fully qualified names in a header file. If those names get too long, you can use a namespace alias to shorten them. (See below.)
 
 ## Declaring namespaces and namespace members
 
@@ -118,7 +118,7 @@ All C++ standard library types and functions are declared in the `std` namespace
 
 ## Nested namespaces
 
-Namespaces may be nested. An ordinary nested namespace has unqualified access to its parent’s members, but the parent members do not have unqualified access to the nested namespace (unless it is declared as inline), as shown in the following example:
+Namespaces may be nested. An ordinary nested namespace has unqualified access to its parent's members, but the parent members do not have unqualified access to the nested namespace (unless it is declared as inline), as shown in the following example:
 
 ```cpp
 namespace ContosoDataServer
@@ -234,7 +234,7 @@ namespace Contoso
 
 ## <a id="namespace_aliases"></a> Namespace aliases
 
-Namespace names need to be unique, which means that often they should not be too short. If the length of a name makes code difficult to read, or is tedious to type in a header file where using directives can’t be used, then you can make a namespace alias which serves as an abbreviation for the actual name. For example:
+Namespace names need to be unique, which means that often they should not be too short. If the length of a name makes code difficult to read, or is tedious to type in a header file where using directives can't be used, then you can make a namespace alias which serves as an abbreviation for the actual name. For example:
 
 ```cpp
 namespace a_very_long_namespace_name { class Foo {}; }

diff --git a/docs/mfc/mfc-desktop-applications.md b/docs/mfc/mfc-desktop-applications.md
@@ -20,7 +20,7 @@ Public and protected class members are documented only when they are normally us
 > [!IMPORTANT]
 > The MFC classes and their members cannot be used in applications that execute in the Windows Runtime environment.
 >
->  MFC libraries (DLLs) for multibyte character encoding (MBCS) are no longer included in Visual Studio, but are available as a Visual Studio add-on. For more information, see [MFC MBCS DLL Add-on](mfc-mbcs-dll-add-on.md).
+> MFC libraries (DLLs) for multibyte character encoding (MBCS) are no longer included in Visual Studio, but are available as a Visual Studio add-on. For more information, see [MFC MBCS DLL Add-on](mfc-mbcs-dll-add-on.md).
 
 ## In This Section