Merge branch 'master' into docs/corob/bad-ticks-part-1-of-n

Author: Colin Robertson

docs/assembler/masm/masm-bnf-grammar.md

@@ -123,15 +123,15 @@ In the example above:
 - **192.168.0.5** is a remote Linux system that was added to the **Connection Manager**.
 - **ubuntu2004** and **debian** are WSL installations.
 
-Select **Manage Connections…** to open the **Connection Manager**.
+Select **Manage Connections** to open the **Connection Manager**.
 
 ### Select a Configure Preset
 
 The dropdown in the middle indicates the active **Configure Preset**. It's the `configurePreset` that's used when CMake is invoked to generate the project build system. This dropdown lists the union of non-hidden Configure Presets defined in `CMakePresets.json` and `CMakeUserPresets.json`.
 
 Visual Studio will use the value of `hostOS` in the Microsoft Visual Studio Settings vendor map to hide Configure Presets that don't apply to the active Target System. For more information, see the entry for `hostOS` in the table under [Visual Studio Settings vendor map](cmake-presets-json-reference.md#visual-studio-settings-vendor-map).
 
-Select **Manage Configurations…** to open the `CMakePresets.json` file located at the root of the project. `CMakePresets.json` is created if it doesn't already exist.
+Select **Manage Configurations** to open the `CMakePresets.json` file located at the root of the project. `CMakePresets.json` is created if it doesn't already exist.
 
 ### Select a Build Preset
 
@@ -169,7 +169,7 @@ Use a forward slash (`/`) for paths in `CMakePresets.json` and `CMakeUserPresets
 
 ### Add new Configure Presets
 
-To add a new Configure Preset to `CMakePresets.json`, from **Solution Explorer** right-click `CMakePresets.json` from **Folder View** and select **Add Configure Preset…** from the context menu. The dialog to select a Configure Preset template appears:
+To add a new Configure Preset to `CMakePresets.json`, from **Solution Explorer** right-click `CMakePresets.json` from **Folder View** and select **Add Configure Preset** from the context menu. The dialog to select a Configure Preset template appears:
 
 ![Add configure preset to `CMakePresets.json` dialog](./media/add-configure-preset-to-cmakepresets.png)
 

docs/build/cmake-presets-vs.md

@@ -42,13 +42,13 @@ You may find it helpful to use the complementary option **`/showResolvedHeader`*
 To build a header unit such as `<vector>` might look like:
 
 ```cmd
-cl … /std:c++latest /exportHeader /headerName:angle vector
+cl . . . /std:c++latest /exportHeader /headerName:angle vector
 ```
 
 Building a local project header such as `"utils/util.h"` might look like:
 
 ```cmd
-cl … /std:c++latest /exportHeader /headerName:quote util/util.h
+cl . . . /std:c++latest /exportHeader /headerName:quote util/util.h
 ```
 
 ### To set this compiler option in the Visual Studio development environment

docs/build/reference/module-exportheader.md

@@ -10,7 +10,7 @@ f1_keywords: ["strcpy_s", "_mbscpy_s", "_mbscpy_s_l", "_tcscpy_s", "wcscpy_s"]
 helpviewer_keywords: ["strcpy_s function", "_tcscpy_s function", "_mbscpy_s function", "_mbscpy_s_l function", "copying strings", "strings [C++], copying", "tcscpy_s function", "wcscpy_s function"]
 ms.assetid: 611326f3-7929-4a5d-a465-a4683af3b053
 ---
-# `strcpy_s`, `wcscpy_`s, `_mbscpy_s`, `_mbscpy_s_l`
+# `strcpy_s`, `wcscpy_s`, `_mbscpy_s`, `_mbscpy_s_l`
 
 Copies a string. These versions of [`strcpy`, `wcscpy`, `_mbscpy`](strcpy-wcscpy-mbscpy.md) have security enhancements, as described in [Security Features in the CRT](../../c-runtime-library/security-features-in-the-crt.md).
 

docs/c-runtime-library/reference/strcpy-s-wcscpy-s-mbscpy-s.md

@@ -64,4 +64,4 @@ This warning is not applicable on Windows 9x and Windows NT version 4 because %p
 
 ## See also
 
-[sprintf, _sprintf_l, swprintf, _swprintf_l, \__swprintf_l](../c-runtime-library/reference/sprintf-sprintf-l-swprintf-swprintf-l-swprintf-l.md)
+[`sprintf, _sprintf_l, swprintf, _swprintf_l, __swprintf_l`](../c-runtime-library/reference/sprintf-sprintf-l-swprintf-swprintf-l-swprintf-l.md)

docs/code-quality/c6273.md

@@ -105,7 +105,7 @@ In Microsoft C++, the tokens **import** and **module** are always identifiers an
 ### Example
 
 ```cpp
-#define foo(…) __VA_ARGS__
+#define foo(...) __VA_ARGS__
 foo(
 import // Always an identifier, never a keyword
 )

docs/cpp/import-export-module.md

@@ -10,7 +10,7 @@ ms.assetid: 52aaec4d-3889-402e-b57d-758078f8ac57
 In Visual C++ you can create ActiveX controls using MFC or ATL.
 
 >[!IMPORTANT]
-> ActiveX is a legacy technology that should not be used for new development. Many capabilities of ActiveX controls can be performed in a simpler and much more secure way with modern technologies such as HTML5 and JavaScript, modern browser extensions, or WebAssembly modules. For more information, see [A break from the past, part 2: Saying goodbye to ActiveX, VBScript, attachEvent…](https://blogs.windows.com/msedgedev/2015/05/06/a-break-from-the-past-part-2-saying-goodbye-to-activex-vbscript-attachevent/) and [Native Messaging](/microsoft-edge/extensions/guides/native-messaging) and [Microsoft Edge extensions](/microsoft-edge/extensions) and [WebAssembly](https://webassembly.org/).
+> ActiveX is a legacy technology that should not be used for new development. Many capabilities of ActiveX controls can be performed in a simpler and much more secure way with modern technologies such as HTML5 and JavaScript, modern browser extensions, or WebAssembly modules. For more information, see [A break from the past, part 2: Saying goodbye to ActiveX, VBScript, attachEvent](https://blogs.windows.com/msedgedev/2015/05/06/a-break-from-the-past-part-2-saying-goodbye-to-activex-vbscript-attachevent/) and [Native Messaging](/microsoft-edge/extensions/guides/native-messaging) and [Microsoft Edge extensions](/microsoft-edge/extensions) and [WebAssembly](https://webassembly.org/).
 
 - [MFC ActiveX Controls](mfc-activex-controls.md)
 

docs/mfc/activex-controls.md

@@ -173,7 +173,7 @@ To avoid the error, remove the **`constexpr`** modifier from the function declar
 In Visual Studio 2019, the `basic_string` range constructor no longer suppresses compiler diagnostics with **`static_cast`**. The following code compiles without warnings in Visual Studio 2017, despite the possible loss of data from **`wchar_t`** to **`char`** when initializing `out`:
 
 ```cpp
-std::wstring ws = /* … */;
+std::wstring ws = /* . . . */;
 std::string out(ws.begin(), ws.end()); // VS2019 C4244: 'argument': conversion from 'wchar_t' to 'const _Elem', possible loss of data.
 ```