Merge pull request #4865 from MicrosoftDocs/main

4/05 AM Publish

Author: huypub

docs/atl/reference/compiler-options-macros.md

@@ -5,7 +5,7 @@ ms.date: 02/01/2023
 f1_keywords: ["_ATL_ALL_WARNINGS", "_ATL_APARTMENT_THREADED", "_ATL_CSTRING_EXPLICIT_CONSTRUCTORS ", "_ATL_ENABLE_PTM_WARNING", "_ATL_FREE_THREADED", "_ATL_MODULES", "_ATL_MULTI_THREADED", "_ATL_NO_AUTOMATIC_NAMESPACE", "_ATL_NO_COM_SUPPORT", "ATL_NO_VTABLE", "ATL_NOINLINE", "_ATL_SINGLE_THREADED"]
 helpviewer_keywords: ["compiler options, macros"]
 ---
-# Compiler Options Macros acrolinx
+# Compiler Options Macros
 
 These macros control specific compiler features.
 

docs/cpp/initializers.md

@@ -180,7 +180,7 @@ Value initialization does the following:
 
 - for classes with at least one public constructor, the default constructor is called
 
-- for non-union classes with no declared constructors, the object is zero-initialized and the default constructor is called
+- for nonunion classes with no declared constructors, the object is zero-initialized and the default constructor is called
 
 - for arrays, every element is value-initialized
 
@@ -520,9 +520,9 @@ Reference-type variables can be declared without initializers only in the follow
     extern int& iVal;
     ```
 
-When initializing a reference-type variable, the compiler uses the decision graph shown in the following figure to select between creating a reference to an object or creating a temporary object to which the reference points.
+When initializing a reference-type variable, the compiler uses the decision graph shown in the following figure to select between creating a reference to an object or creating a temporary object to which the reference points:
 
-::image type="complex" source="../cpp/media/vc38s71.gif" alt-text="Decision graph for initialization of reference types.":::
+:::image type="complex" source="../cpp/media/vc38s71.gif" alt-text="Decision graph for initialization of reference types.":::
 The decision graph begins with: is the initializer an lvalue of the same type or a type derived from the type of reference? If yes, the reference refers to the object specified in the initializer. If no, the next decision is whether the reference-type variable is a const T reference being initialized and can the initializer be implicitly converted to a T? If yes, the temporary is created and the reference variable becomes a name for that temporary. If no, it's an error.
 :::image-end:::
 Decision graph for initialization of reference types