Merge branch 'main' of https://github.com/MicrosoftDocs/cpp-docs-pr into RAS-cpp-US1921538-1

Author: rachana-satao

docs/atl-mfc-shared/cstring-argument-passing.md

@@ -14,9 +14,9 @@ When you define a class interface, you must determine the argument-passing conve
 
 ## <a name="_core_strings_as_function_inputs"></a> Strings as Function Inputs
 
-The most efficient and secure way to use a `CString` object in called functions is to pass a `CString` object to the function. Despite the name, a `CString` object doesn't store a string internally as a C-style string that has a `NULL` terminator. Instead, a `CString` object keeps careful track of the number of characters it has. Having `CString` provide a `LPCTSTR` pointer to a `NULL` terminated string is a small amount of work that can become significant if your code has to do it constantly. The result is temporary because any change to the `CString` contents invalidates old copies of the `LPCTSTR` pointer.
+The most efficient and secure way to use a `CString` object in called functions is to pass a `CString` object to the function. Despite the name, a `CString` object doesn't store a string internally as a C-style string that has a `NULL` terminator. Instead, a `CString` object keeps careful track of the number of characters it has. Having `CString` provide a `LPCTSTR` pointer to a `NULL`-terminated string is a small amount of work that can become significant if your code has to do it constantly. The result is temporary because any change to the `CString` contents invalidates old copies of the `LPCTSTR` pointer.
 
-It does make sense in some cases to provide a C-style string. For example, there can be a situation where a called function is written in C and doesn't support objects. In this case, coerce the `CString` parameter to `LPCTSTR`, and the function will get a C-style `NULL` terminated string. You can also go the other direction and create a `CString` object by using the `CString` constructor that accepts a C-style string parameter.
+It does make sense in some cases to provide a C-style string. For example, there can be a situation where a called function is written in C and doesn't support objects. In this case, coerce the `CString` parameter to `LPCTSTR`, and the function will get a C-style `NULL`-terminated string. You can also go the other direction and create a `CString` object by using the `CString` constructor that accepts a C-style string parameter.
 
 If the string contents are to be changed by a function, declare the parameter as a nonconstant `CString` reference (`CString&`).
 

docs/atl-mfc-shared/string-data-management.md

@@ -8,7 +8,7 @@ helpviewer_keywords: ["Unicode, string objects"]
 
 Visual C++ provides several ways to manage string data:
 
-- [String Manipulation](../c-runtime-library/string-manipulation-crt.md) for working with C-style `NULL` terminated strings
+- [String Manipulation](../c-runtime-library/string-manipulation-crt.md) for working with C-style `NULL`-terminated strings
 
 - Win32 API functions for managing strings
 

docs/atl/reference/cregkey-class.md

@@ -83,7 +83,7 @@ class CRegKey
 When you close a key, its registry data is written (flushed) to the hard disk. This process may take several seconds. If your application must explicitly write registry data to the hard disk, you can call the [`RegFlushKey`](/windows/win32/api/winreg/nf-winreg-regflushkey) Win32 function. However, `RegFlushKey` uses many system resources and should be called only when absolutely necessary.
 
 > [!IMPORTANT]
-> Any methods that allow the caller to specify a registry location have the potential to read data that cannot be trusted. Methods that make use of [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) should take into consideration that this function does not explicitly handle strings which are `NULL` terminated. Both conditions should be checked for by the calling code.
+> Any methods that allow the caller to specify a registry location have the potential to read data that cannot be trusted. Methods that make use of [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) should take into consideration that this function does not explicitly handle strings which are null-terminated. Both conditions should be checked for by the calling code.
 
 ## Requirements
 
@@ -469,7 +469,7 @@ LONG QueryBinaryValue(
 ### Parameters
 
 *`pszValueName`*\
-Pointer to a `NULL` terminated string containing the name of the value to query.
+Pointer to a `NULL`-terminated string containing the name of the value to query.
 
 *`pValue`*\
 Pointer to a buffer that receives the value's data.
@@ -486,7 +486,7 @@ If the method succeeds, `ERROR_SUCCESS` is returned. If the method fails to read
 This method makes use of `RegQueryValueEx` and confirms that the correct type of data is returned. See [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) for more details.
 
 > [!IMPORTANT]
-> This method allows the caller to specify any registry location, potentially reading data which cannot be trusted. Also, the [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) function used by this method does not explicitly handle strings which are `NULL` terminated. Both conditions should be checked for by the calling code.
+> This method allows the caller to specify any registry location, potentially reading data which cannot be trusted. Also, the [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) function used by this method does not explicitly handle strings which are null-terminated. Both conditions should be checked for by the calling code.
 
 ## <a name="querydwordvalue"></a> `CRegKey::QueryDWORDValue`
 
@@ -501,7 +501,7 @@ LONG QueryDWORDValue(
 ### Parameters
 
 *`pszValueName`*\
-Pointer to a `NULL` terminated string containing the name of the value to query.
+Pointer to a `NULL`-terminated string containing the name of the value to query.
 
 *`dwValue`*\
 Pointer to a buffer that receives the `DWORD`.
@@ -515,7 +515,7 @@ If the method succeeds, `ERROR_SUCCESS` is returned. If the method fails to read
 This method makes use of `RegQueryValueEx` and confirms that the correct type of data is returned. See [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) for more details.
 
 > [!IMPORTANT]
-> This method allows the caller to specify any registry location, potentially reading data which cannot be trusted. Also, the [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) function used by this method does not explicitly handle strings which are `NULL` terminated. Both conditions should be checked for by the calling code.
+> This method allows the caller to specify any registry location, potentially reading data which cannot be trusted. Also, the [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) function used by this method does not explicitly handle strings which are null-terminated. Both conditions should be checked for by the calling code.
 
 ## <a name="queryguidvalue"></a> `CRegKey::QueryGUIDValue`
 
@@ -530,7 +530,7 @@ LONG QueryGUIDValue(
 ### Parameters
 
 *`pszValueName`*\
-Pointer to a `NULL` terminated string containing the name of the value to query.
+Pointer to a `NULL`-terminated string containing the name of the value to query.
 
 *`guidValue`*\
 Pointer to a variable that receives the GUID.
@@ -560,10 +560,10 @@ LONG QueryMultiStringValue(
 ### Parameters
 
 *`pszValueName`*\
-Pointer to a `NULL` terminated string containing the name of the value to query.
+Pointer to a `NULL`-terminated string containing the name of the value to query.
 
 *`pszValue`*\
-Pointer to a buffer that receives the multistring data. A multistring is an array of `NULL` terminated strings, terminated by two null characters.
+Pointer to a buffer that receives the multistring data. A multistring is an array of `NULL`-terminated strings, terminated by two null characters.
 
 *`pnChars`*\
 The size, in `TCHARs`, of the buffer pointed to by *`pszValue`*. When the method returns, *`pnChars`* contains the size, in `TCHARs`, of the multistring retrieved, including a terminating null character.
@@ -577,7 +577,7 @@ If the method succeeds, `ERROR_SUCCESS` is returned. If the method fails to read
 This method makes use of `RegQueryValueEx` and confirms that the correct type of data is returned. See [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) for more details.
 
 > [!IMPORTANT]
-> This method allows the caller to specify any registry location, potentially reading data which cannot be trusted. Also, the [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) function used by this method does not explicitly handle strings which are `NULL` terminated. Both conditions should be checked for by the calling code.
+> This method allows the caller to specify any registry location, potentially reading data which cannot be trusted. Also, the [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) function used by this method does not explicitly handle strings which are null-terminated. Both conditions should be checked for by the calling code.
 
 ## <a name="queryqwordvalue"></a> `CRegKey::QueryQWORDValue`
 
@@ -592,7 +592,7 @@ LONG QueryQWORDValue(
 ### Parameters
 
 *`pszValueName`*\
-Pointer to a `NULL` terminated string containing the name of the value to query.
+Pointer to a `NULL`-terminated string containing the name of the value to query.
 
 *`qwValue`*\
 Pointer to a buffer that receives the `QWORD`.
@@ -606,7 +606,7 @@ If the method succeeds, `ERROR_SUCCESS` is returned. If the method fails to read
 This method makes use of `RegQueryValueEx` and confirms that the correct type of data is returned. See [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) for more details.
 
 > [!IMPORTANT]
-> This method allows the caller to specify any registry location, potentially reading data which cannot be trusted. Also, the [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) function used by this method does not explicitly handle strings which are `NULL` terminated. Both conditions should be checked for by the calling code.
+> This method allows the caller to specify any registry location, potentially reading data which cannot be trusted. Also, the [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) function used by this method does not explicitly handle strings which are null-terminated. Both conditions should be checked for by the calling code.
 
 ## <a name="querystringvalue"></a> `CRegKey::QueryStringValue`
 
@@ -622,7 +622,7 @@ LONG QueryStringValue(
 ### Parameters
 
 *`pszValueName`*\
-Pointer to a `NULL` terminated string containing the name of the value to query.
+Pointer to a `NULL`-terminated string containing the name of the value to query.
 
 *`pszValue`*\
 Pointer to a buffer that receives the string data.
@@ -639,7 +639,7 @@ If the method succeeds, `ERROR_SUCCESS` is returned. If the method fails to read
 This method makes use of `RegQueryValueEx` and confirms that the correct type of data is returned. See [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) for more details.
 
 > [!IMPORTANT]
-> This method allows the caller to specify any registry location, potentially reading data which cannot be trusted. Also, the [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) function used by this method does not explicitly handle strings which are `NULL` terminated. Both conditions should be checked for by the calling code.
+> This method allows the caller to specify any registry location, potentially reading data which cannot be trusted. Also, the [`RegQueryValueEx`](/windows/win32/api/winreg/nf-winreg-regqueryvalueexw) function used by this method does not explicitly handle strings which are null-terminated. Both conditions should be checked for by the calling code.
 
 ## <a name="queryvalue"></a> `CRegKey::QueryValue`
 
@@ -665,7 +665,7 @@ ATL_DEPRECATED LONG QueryValue(
 ### Parameters
 
 *`pszValueName`*\
-Pointer to a `NULL` terminated string containing the name of the value to query. If *`pszValueName`* is `NULL` or an empty string, `""`, the method retrieves the type and data for the key's unnamed or default value, if any.
+Pointer to a `NULL`-terminated string containing the name of the value to query. If *`pszValueName`* is `NULL` or an empty string, `""`, the method retrieves the type and data for the key's unnamed or default value, if any.
 
 *`pdwType`*\
 Pointer to a variable that receives a code indicating the type of data stored in the specified value. The *`pdwType`* parameter can be `NULL` if the type code isn't required.
@@ -699,7 +699,7 @@ The two original versions of `QueryValue` are no longer supported and are marked
 The remaining method calls `RegQueryValueEx`.
 
 > [!IMPORTANT]
-> This method allows the caller to specify any registry location, potentially reading data which cannot be trusted. Also, the `RegQueryValueEx` function used by this method does not explicitly handle strings which are `NULL` terminated. Both conditions should be checked for by the calling code.
+> This method allows the caller to specify any registry location, potentially reading data which cannot be trusted. Also, the `RegQueryValueEx` function used by this method does not explicitly handle strings which are null-terminated. Both conditions should be checked for by the calling code.
 
 ## <a name="recursedeletekey"></a> `CRegKey::RecurseDeleteKey`
 
@@ -875,7 +875,7 @@ LONG SetMultiStringValue(LPCTSTR pszValueName, LPCTSTR pszValue) throw();
 Pointer to a string containing the name of the value to set. If a value with this name isn't already present, the method adds it to the key.
 
 *`pszValue`*\
-Pointer to the multistring data to be stored with the specified value name. A multistring is an array of `NULL` terminated strings, terminated by two null characters.
+Pointer to the multistring data to be stored with the specified value name. A multistring is an array of `NULL`-terminated strings, terminated by two null characters.
 
 ### Return Value
 

docs/build/cmake-remote-debugging.md

@@ -60,7 +60,7 @@ Select the Visual Studio **Configuration** dropdown and select **Manage Configur
 ![Choose Manage Configurations in the Visual Studio configurations drop-down.](media/vs2019-cmake-manage-configurations.png)
 
 Add a new configuration by selecting **Add a new configuration** (the green **+** button).\
-In the **CMakeSettings** dialog that appears, select **arm64-debug**, and then press **Select**:
+In the **CMakeSettings** dialog that appears, select **arm64-debug**, and then choose **Select**:
 
 ![Add arm64-debug configuration.](media/cmake-add-config-icon-with-target-dialog.png)
 
@@ -71,13 +71,12 @@ The **Toolset** dropdown is set to **msvc_arm64_x64**. Your settings should now
 ![CMake settings dialog.](media/cmake-settings-editor2.png)
 
 > [!Note]
-> In the **Toolset** dropdown, **msvc_arm64** selects 32-bit host tools to cross-compile to ARM64, whereas **msvc_arm64 x64** selects 64-bit host tools to cross-compile to ARM64, which is what you'll do in this tutorial.
+> In the **Toolset** dropdown, **msvc_arm64** selects 32-bit host tools to cross-compile to ARM64, whereas **msvc_arm64 x64** selects 64-bit host tools to cross-compile to ARM64, which is what you'll do in this tutorial. For more information about the available toolset environments, see [Pre-defined environments](cppproperties-schema-reference.md#pre-defined-environments).
 
 Save the *`CMakeSettings.json`* file. In the configuration dropdown, select **arm64-debug**. (It may take a moment after saving the *`CMakeSettings.json`* file for it to appear in the list):
 
 ![Ensure that arm64-debug is selected in the Visual Studio configurations drop-down.](media/vs2019-cmake-manage-configurations-arm.png)
 
-
 ## Add a debug configuration file
 
 Next, add configuration information that tells Visual Studio where to find your remote machine, along with other configuration details.

docs/build/formatting-the-output-of-a-custom-build-step-or-build-event.md

@@ -1,40 +1,42 @@
 ---
-description: "Learn more about: Formatting the Output of a Custom Build Step or Build Event"
-title: "Formatting the Output of a Custom Build Step or Build Event"
-ms.date: "08/27/2018"
+description: "Learn more about: Formatting the output of a custom build step or build event"
+title: "Formatting the output of a custom build step or build event"
+ms.date: 03/15/2022
 helpviewer_keywords: ["builds [C++], build events", "custom build steps [C++], output format", "events [C++], build", "build events [C++], output format", "build steps [C++], output format", "builds [C++], custom build steps"]
 ms.assetid: 92ad3e38-24d7-4b89-90e6-5a16f5f998da
 ---
-# Formatting the Output of a Custom Build Step or Build Event
+# Formatting the output of a custom build step or build event
 
 If the output of a custom build step or build event is formatted correctly, users get the following benefits:
 
 - Warnings and errors are counted in the **Output** window.
 
 - Output appears in the **Task List** window.
 
-- Clicking on the output in the **Output** window displays the appropriate topic.
+- Clicking on the output in the **Output** window displays the appropriate location.
 
-- F1 operations are enabled in the **Task List** window or **Output** window.
+- **F1** operations are enabled in the **Task List** window or **Output** window.
+
+## Output format
 
 The format of the output should be:
 
-> {<em>filename</em>**(**<em>line#</em> \[**,** <em>column#</em>]**)** \| *toolname*} **:** \[ <em>any text</em> ] {**error** \| **warning**} <em>code+number</em>**:**<em>localizable string</em> \[ <em>any text</em> ]
+> { *filename*`(`*line-number* \[`,` *column-number*]`)` \| *tool-name* } `:` \[ *any-text* ] {`error` \| `warning`} *code-type-and-number* `:` *localizable-string* \[ *any-text* ]
 
 Where:
 
-- {*a* \| *b*} is a choice of either *a* or *b*.
+- { *a* \| *b* } is a choice of either *a* or *b*,
 
-- \[<em>item</em>] is an optional string or parameter.
+- \[ *item* ] is an optional string or parameter,
 
-- **Bold** represents a literal.
+- `text` represents a literal.
 
 For example:
 
-> C:\\*sourcefile.cpp*(134) : error C2143: syntax error : missing ';' before '}'
+> C:\\sourcefile.cpp(134) : error C2143: syntax error : missing ';' before '}'
 >
-> LINK : fatal error LNK1104: cannot open file '*somelib.lib*'
+> LINK : fatal error LNK1104: cannot open file 'some-library.lib'
 
 ## See also
 
-[Understanding Custom Build Steps and Build Events](understanding-custom-build-steps-and-build-events.md)
+[Understanding custom build steps and build events](understanding-custom-build-steps-and-build-events.md)