acrolinx

Author: TylerMSFT

docs/cpp/cpp-bit-fields.md

@@ -32,7 +32,7 @@ struct Date {
 };
 ```
 
-The conceptual memory layout of an object of type `Date` is shown in the following figure.
+The conceptual memory layout of an object of type `Date` is shown in the following figure:
 
 :::image type="complex" source="../cpp/media/vc38uq1.png" alt-text="Memory layout of a date object, showing where the nWeekDay, nMonthDay, nMonth, and nYear bit fields fall.":::
 32 bits of memory are displayed in a row. Starting with the least significant bit, 3 bits are for nWeekDay. The next 6 bits are for nMonthDay. The next 5 bits are for nMonth. The next 2 bits are unused. The next 8 bits are for nYear. The remaining 8 bits are unused.
@@ -46,7 +46,7 @@ The ordering of data declared as bit fields is from low to high bit, as shown in
 
 **END Microsoft Specific**
 
-If the declaration of a structure includes an unnamed field of length 0, as shown in the following example,
+If the declaration of a structure includes an unnamed field of length 0, as shown in the following example:
 
 ```cpp
 // bit_fields2.cpp
@@ -60,7 +60,7 @@ struct Date {
 };
 ```
 
-then the memory layout is as shown in the following figure:
+Then the memory layout is as shown in the following figure:
 
 :::image type="complex" source="../cpp/media/vc38uq2.png" alt-text="Layout of a Date object with a zero length bit field, which forces alignment padding.":::
 64 bits of memory are displayed in a row. Starting with the least significant bit, 5 bits are for nMonth. The next 8 bits are for nYear. The next 19 bits are unused. The next 3 bits are for nWeekDay. The next 6 bits are for nMonthDay. The remaining bits are unused.

docs/cpp/dynamic-cast-operator.md

@@ -23,11 +23,11 @@ See [static_cast](../cpp/static-cast-operator.md) for an explanation of the diff
 
 There are two breaking changes in the behavior of **`dynamic_cast`** in managed code:
 
-- **`dynamic_cast`** to a pointer to the underlying type of a boxed enum fails at runtime, returning 0 instead of the converted pointer.
+- **`dynamic_cast`** to a pointer to the underlying type of a boxed enum will fail at runtime, returning 0 instead of the converted pointer.
 
-- **`dynamic_cast`** won't throw an exception when `type-id` is an interior pointer to a value type; instead, the cast fails at runtime. The cast returns the 0 pointer value instead of throwing.
+- **`dynamic_cast`** will no longer throw an exception when `type-id` is an interior pointer to a value type; instead, the cast fails at runtime. The cast returns the 0 pointer value instead of throwing.
 
-If `type-id` is a pointer to an unambiguous accessible direct or indirect base class of `expression`; a pointer to the unique subobject of type `type-id` is the result. For example:
+If `type-id` is a pointer to an unambiguous accessible direct or indirect base class of `expression`, then a pointer to the unique subobject of type `type-id` is the result. For example:
 
 ```cpp
 // dynamic_cast_1.cpp

docs/cpp/member-access-control-cpp.md

@@ -228,7 +228,7 @@ In the preceding example, calling the virtual function `GetState` using a pointe
 
 ## Access control with multiple inheritance
 
-In multiple-inheritance lattices involving virtual base classes, a given name can be reached through more than one path. Because different access control can be applied along these different paths, the compiler chooses the path that gives the most access. See the following figure.
+In multiple-inheritance lattices involving virtual base classes, a given name can be reached through more than one path. Because different access control can be applied along these different paths, the compiler chooses the path that gives the most access. See the following figure:
 
 :::image type="complex" source="../cpp/media/vc38v91.gif" alt-text="Diagram showing access along the paths of an inheritance graph.":::
 The diagram shows the following inheritance hierarchy: class VBase is the base class. Class LeftPath inherits from VBase using virtual private VBase. class RightPath also inherits from VBase but using virtual public VBase. Finally, class Derived inherits from both class LeftPath and class RightPath using public LeftPath, public RightPath.

docs/cpp/unions.md

@@ -533,7 +533,7 @@ int main()
 */
 ```
 
-The `NumericType` union is arranged in memory (conceptually) as shown in the following figure.
+The `NumericType` union is arranged in memory (conceptually) as shown in the following figure:
 
 :::image type="complex" source="../cpp/media/vc38ul1.png" alt-text="Diagram that shows the overlapping storage of data in the NumericType union.":::
 The diagram shows 8 bytes of data. The double type dValue occupies the entire 8 bytes. The type long lValue occupies the first 4 bytes. The short type iValue occupies the first byte.

docs/mfc/reference/cdc-class.md

@@ -2836,10 +2836,10 @@ A pointer to a `CBrush` object if successful; otherwise `NULL`.
 
 ### Remarks
 
-A halftone brush shows pixels that are alternately foreground and background colors to create a dithered pattern. The following is an example of a dithered pattern created by a halftone brush.
+A halftone brush shows pixels that are alternately foreground and background colors to create a dithered pattern. The following diagram shows an example of a dithered pattern created by a halftone brush:
 
 :::image type="complex" source="../../mfc/reference/media/vc318s1.gif" alt-text="Detail of a dithered pen stroke.":::
-The diagram shows how the background color of black and the foreground color of yellow are combined into a pattern where the black and yellow pixels alternate with each other to create a dithered pen stroke.
+The diagram shows how the background color of black, and the foreground color of yellow, are combined into a pattern by alternating the black and yellow pixels with each other to create a dithered pen stroke.
 :::image-end:::  
 
 ## <a name="getkerningpairs"></a> `CDC::GetKerningPairs`