RomandevJavaScript
diff --git a/‎docs/build/reference/arch-arm64.md‎
Lines changed: 7 additions & 5 deletions b/‎docs/build/reference/arch-arm64.md‎
Lines changed: 7 additions & 5 deletions
diff --git a/‎docs/build/reference/fr-fr-create-dot-sbr-file.md‎
Lines changed: 23 additions & 22 deletions b/‎docs/build/reference/fr-fr-create-dot-sbr-file.md‎
Lines changed: 23 additions & 22 deletions
diff --git a/‎docs/error-messages/compiler-warnings/compiler-warning-level-1-and-level-4-c4700.md‎
Lines changed: 9 additions & 5 deletions b/‎docs/error-messages/compiler-warnings/compiler-warning-level-1-and-level-4-c4700.md‎
Lines changed: 9 additions & 5 deletions
diff --git a/‎docs/error-messages/compiler-warnings/compiler-warning-level-1-c4532.md‎
Lines changed: 13 additions & 7 deletions b/‎docs/error-messages/compiler-warnings/compiler-warning-level-1-c4532.md‎
Lines changed: 13 additions & 7 deletions
diff --git a/‎docs/error-messages/compiler-warnings/compiler-warning-level-1-c4533.md‎
Lines changed: 11 additions & 3 deletions b/‎docs/error-messages/compiler-warnings/compiler-warning-level-1-c4533.md‎
Lines changed: 11 additions & 3 deletions
diff --git a/‎docs/error-messages/compiler-warnings/compiler-warning-level-1-c4789.md‎
Lines changed: 7 additions & 5 deletions b/‎docs/error-messages/compiler-warnings/compiler-warning-level-1-c4789.md‎
Lines changed: 7 additions & 5 deletions
diff --git a/‎docs/error-messages/compiler-warnings/compiler-warning-level-2-c4146.md‎
Lines changed: 4 additions & 2 deletions b/‎docs/error-messages/compiler-warnings/compiler-warning-level-2-c4146.md‎
Lines changed: 4 additions & 2 deletions
diff --git a/‎docs/error-messages/compiler-warnings/compiler-warning-level-2-c4308.md‎
Lines changed: 6 additions & 2 deletions b/‎docs/error-messages/compiler-warnings/compiler-warning-level-2-c4308.md‎
Lines changed: 6 additions & 2 deletions
diff --git a/‎docs/error-messages/compiler-warnings/compiler-warning-level-3-c4995.md‎
Lines changed: 8 additions & 4 deletions b/‎docs/error-messages/compiler-warnings/compiler-warning-level-3-c4995.md‎
Lines changed: 8 additions & 4 deletions
@@ -1,24 +1,26 @@
 ---
 description: "Learn more about: /arch (ARM64)"
 title: "/arch (ARM64)"
-ms.date: 06/30/2022
+ms.date: 08/30/2022
 ---
 # `/arch` (ARM64)
 
 Specifies the architecture for code generation on ARM64. For more information on **`/arch`** for other target architectures, see [`/arch` (x86)](arch-x86.md), [`/arch` (x64)](arch-x64.md), and [`/arch` (ARM)](arch-arm.md).
 
 ## Syntax
 
-> **`/arch:`**\[**`armv8.0`**|**`armv8.8`**]
+> **`/arch:`**\[**`armv8.0`**-**`armv8.8`**]
 
 ## Arguments
 
-**`/arch:armv8.0`** or **`/arch:armv8.8`**\
+**`/arch:armv8.0`** through **`/arch:armv8.8`**\
 Optional. Specifies minimum CPU extension requirements for ARMv8.x-A. The default is **`/arch:armv8.0`**.
 
 ## Remarks
 
-The `_M_ARM64` macro is defined by default when compiling for an ARM64 target. For more information, see [Predefined Macros](../../preprocessor/predefined-macros.md).
+You may specify a CPU extension requirement from Armv8.0-A through Armv8.8-A. However, depending on your version of Visual Studio, the compiler may not yet generate instructions from all feature sets required by the extension level you specify. For example, **`/arch:armv8.1`** allows the `_Interlocked*` intrinsic functions to use the appropriate atomic instruction that was introduced with the ARMv8.1 extension, FEAT_LSE, but compiler support requires Visual Studio 2022 version 17.2 or later.
+
+The `_M_ARM64` macro is defined by default when compiling for an ARM64 target. For more information, see [Predefined macros](../../preprocessor/predefined-macros.md).
 
 When you use [`/clr`](clr-common-language-runtime-compilation.md) to compile, **`/arch`** has no effect on code generation for managed functions. **`/arch`** only affects code generation for native functions.
 
@@ -28,7 +30,7 @@ When you use [`/clr`](clr-common-language-runtime-compilation.md) to compile, **
 
 1. Select the **Configuration Properties** > **C/C++** > **Command Line** property page.
 
-1. In the **Additional options** box, add *`/arch:armv8.0`* or *`/arch:armv8.8`*. Choose **OK** to save your changes.
+1. In the **Additional options** box, add *`/arch:armv8.0`* or higher. Choose **OK** to save your changes.
 
 ### To set this compiler option programmatically
 
 
@@ -1,39 +1,40 @@
 ---
-description: "Learn more about: /FR, /Fr (Create .Sbr File)"
-title: "/FR, /Fr (Create .Sbr File)"
-ms.date: "11/04/2016"
+description: "Learn more about: /FR, /Fr (Name SBR file)"
+title: "/FR, /Fr (Name SBR file)"
+ms.date: 08/30/2022
 f1_keywords: ["VC.Project.VCCLWCECompilerTool.BrowseInformation", "VC.Project.VCCLCompilerTool.BrowseInformation", "/fr", "VC.Project.VCCLCompilerTool.BrowseInformationFile", "VC.Project.VCCLWCECompilerTool.BrowseInformationFile"]
 helpviewer_keywords: ["/FR compiler option [C++]", "-FR compiler option [C++]", "FR compiler option [C++]", "symbolic browser information"]
 ms.assetid: 3fd8f88b-3924-4feb-9393-287036a28896
 ---
-# /FR, /Fr (Create .Sbr File)
+# `/FR`, `/Fr` (Name SBR file)
 
-Creates .sbr files.
+Creates *`.sbr`* (source browser) files, used by [Code maps](/visualstudio/modeling/code-maps-for-cpp), BSCMAKE, and some third-party code browsing tools.
 
 ## Syntax
 
-```
-/FR[pathname[\filename]]
-/Fr[pathname[\filename]]
-```
+> **`/FR`**\[*`pathname`*\[*`\filename`*]]\
+> **`/Fr`**\[*`pathname`*\[*`\filename`*]]
 
-## Remarks
+### Arguments
+
+*`pathname`*\
+The optional destination directory for the generated *`.sbr`* files. If this value isn't specified, the files are created in the default output directory. For more information, see [Specifying the pathname](specifying-the-pathname.md).
 
-> [!WARNING]
-> Although BSCMAKE is still installed with Visual Studio, it is no longer used by the IDE. Since Visual Studio 2008, browse and symbol information is stored automatically in a SQL Server .sdf file in the solution folder.
+*`filename`*\
+An optional filename for the generated *`.sbr`* file. If this value isn't specified, the compiler uses the base name of the source file with a *`.sbr`* extension. For more information, see [Specifying the pathname](specifying-the-pathname.md).
 
-During the build process, the Microsoft Browse Information File Maintenance Utility (BSCMAKE) uses these files to create a .BSC file, which is used to display browse information.
+## Remarks
 
-**/FR** creates an .sbr file with complete symbolic information.
+**`/FR`** creates an *`.sbr`* file with complete symbolic information.
 
-**/Fr** creates an .sbr file without information on local variables.
+**`/Fr`** creates an *`.sbr`* file without information on local variables. **`/Fr`** is deprecated; use **`/FR`** instead. For more information, see the Deprecated and removed compiler options section in [Compiler options listed by category](compiler-options-listed-by-category.md).
 
-If you do not specify `filename`, the .sbr file gets the same base name as the source file.
+The Visual Studio [Code Maps](/visualstudio/modeling/code-maps-for-cpp) feature requires the *`.sbr`* files generated by **`/FR`**.
 
-**/Fr** is deprecated; use **/FR** instead. For more information, see Deprecated and Removed Compiler Options in [Compiler Options Listed by Category](compiler-options-listed-by-category.md).
+The Microsoft Browse Information File Maintenance Utility (BSCMAKE) uses *`.sbr`* files to create a *`.bsc`* file, used to display browse information in some third-party tools. For more information, see [BSCMAKE reference](bscmake-reference.md).
 
 > [!NOTE]
-> Do not change the .sbr extension. BSCMAKE requires the intermediary files to have that extension.
+> Although BSCMAKE is still installed with Visual Studio, it's no longer used by the IDE. Since Visual Studio 2008, browse and symbol information is stored automatically in a SQL Server SDF file in the solution folder. If you use BSCMAKE, don't change the *`.sbr`* extension. BSCMAKE requires the intermediate files to have that extension.
 
 ### To set this compiler option in the Visual Studio development environment
 
@@ -49,7 +50,7 @@ If you do not specify `filename`, the .sbr file gets the same base name as the s
 
 ## See also
 
-[Output-File (/F) Options](output-file-f-options.md)<br/>
-[MSVC Compiler Options](compiler-options.md)<br/>
-[MSVC Compiler Command-Line Syntax](compiler-command-line-syntax.md)<br/>
-[Specifying the Pathname](specifying-the-pathname.md)
+[Output-File (`/F`) options](output-file-f-options.md)\
+[MSVC compiler options](compiler-options.md)\
+[MSVC compiler command-line syntax](compiler-command-line-syntax.md)\
+[Specifying the pathname](specifying-the-pathname.md)
@@ -1,7 +1,7 @@
 ---
 description: "Learn more about: Compiler Warning (level 1 and level 4) C4700"
 title: "Compiler Warning (level 1 and level 4) C4700"
-ms.date: "02/21/2018"
+ms.date: 08/30/2022
 f1_keywords: ["C4700"]
 helpviewer_keywords: ["C4700"]
 ms.assetid: 2da0deb4-77dd-4b05-98d3-b78d74ac4ca7
@@ -10,13 +10,17 @@ ms.assetid: 2da0deb4-77dd-4b05-98d3-b78d74ac4ca7
 
 > uninitialized local variable '*name*' used
 
-The local variable *name* has been *used*, that is, read from, before it has been assigned a value. In C and C++, local variables are not initialized by default. Uninitialized variables can contain any value, and their use leads to undefined behavior. Warning C4700 almost always indicates a bug that can cause unpredictable results or crashes in your program.
+## Remarks
 
-To fix this issue, you can initialize local variables when they are declared, or assign a value to them before they are used. A function can be used to initialize a variable that's passed as a reference parameter, or when its address is passed as a pointer parameter.
+The local variable *name* has been *used*, that is, read from, before it has been assigned a value. In C and C++, local variables aren't initialized by default. Uninitialized variables can contain any value, and their use leads to undefined behavior. Warning C4700 almost always indicates a bug that can cause unpredictable results or crashes in your program.
+
+To fix this issue, you can initialize local variables when they're declared, or assign a value to them before they're used. A function can be used to initialize a variable that's passed as a reference parameter, or when its address is passed as a pointer parameter.
+
+The [`/sdl` (Enable Additional Security Checks)](../../build/reference/sdl-enable-additional-security-checks.md) compiler option elevates this warning to an error.
 
 ## Example
 
-This sample generates C4700 when variables t, u, and v are used before they are initialized, and shows the kind of garbage value that can result. Variables x, y, and z do not cause the warning, because they are initialized before use:
+This sample generates C4700 when variables `t`, `u`, and `v` are used before they're initialized, and shows the kind of garbage value that can result. Variables `x`, `y`, and `z` don't cause the warning, because they're initialized before use:
 
 ```cpp
 // c4700.cpp
@@ -46,7 +50,7 @@ int main()
 }
 ```
 
-When this code is run, t, u, and v are uninitialized, and the output for s is unpredictable:
+When this code is run, `t`, `u`, and `v` are uninitialized, and the output for `s` is unpredictable:
 
 ```Output
 Value in s: 37816963
 
@@ -1,30 +1,36 @@
 ---
 description: "Learn more about: Compiler Warning (level 1) C4532"
 title: "Compiler Warning (level 1) C4532"
-ms.date: "11/04/2016"
+ms.date: 08/30/2022
 f1_keywords: ["C4532"]
 helpviewer_keywords: ["C4532"]
 ms.assetid: 4e2a286a-d233-4106-9f65-29be1a94ca02
 ---
 # Compiler Warning (level 1) C4532
 
-'continue' : jump out of __finally/finally block has undefined behavior during termination handling
+> 'continue' : jump out of __finally/finally block has undefined behavior during termination handling
+
+## Remarks
 
 The compiler encountered one of the following keywords:
 
-- [continue](../../cpp/continue-statement-cpp.md)
+- [`continue`](../../cpp/continue-statement-cpp.md)
 
-- [break](../../cpp/break-statement-cpp.md)
+- [`break`](../../cpp/break-statement-cpp.md)
 
-- [goto](../../cpp/goto-statement-cpp.md)
+- [`goto`](../../cpp/goto-statement-cpp.md)
 
-causing a jump out of a [__finally](../../cpp/try-finally-statement.md) or [finally](../../dotnet/finally.md) block during abnormal termination.
+causing a jump out of a [`__finally`](../../cpp/try-finally-statement.md) or [`finally`](../../dotnet/finally.md) block during abnormal termination.
 
 If an exception occurs, and while the stack is being unwound during execution of the termination handlers (the **`__finally`** or finally blocks), and your code jumps out of a **`__finally`** block before the **`__finally`** block ends, the behavior is undefined. Control may not return to the unwinding code, so the exception may not be handled properly.
 
 If you must jump out of a **`__finally`** block, check for abnormal termination first.
 
-The following sample generates C4532; simply comment out the jump statements to resolve the warnings.
+The [`/sdl` (Enable Additional Security Checks)](../../build/reference/sdl-enable-additional-security-checks.md) compiler option elevates this warning to an error.
+
+## Example
+
+The following sample generates C4532; delete or comment out the jump statements to resolve the warnings.
 
 ```cpp
 // C4532.cpp
 
@@ -1,16 +1,24 @@
 ---
 description: "Learn more about: Compiler Warning (level 1) C4533"
 title: "Compiler Warning (level 1) C4533"
-ms.date: "11/04/2016"
+ms.date: 08/30/2022
 f1_keywords: ["C4533"]
 helpviewer_keywords: ["C4533"]
 ms.assetid: 359fecda-d540-46e5-b214-dbabe9ef50d2
 ---
 # Compiler Warning (level 1) C4533
 
-initialization of 'variable' is skipped by 'instruction'
+> initialization of '*variable*' is skipped by '*instruction*'
 
-An instruction in your program changed the flow of control, such that, an instruction that initialized a variable was not executed. The following sample generates C4533:
+## Remarks
+
+An instruction in your program changed the flow of control, so an instruction that initialized a variable wasn't executed.
+
+The [`/sdl` (Enable Additional Security Checks)](../../build/reference/sdl-enable-additional-security-checks.md) compiler option elevates this warning to an error.
+
+## Example
+
+The following sample generates C4533. To resolve the issue, move the initialization before the jump instruction or after the target of the jump.
 
 ```cpp
 // C4533.cpp
 
@@ -1,7 +1,7 @@
 ---
 description: "Learn more about: Compiler Warning (Level 1) C4789"
 title: "Compiler Warning (Level 1) C4789"
-ms.date: "03/25/2019"
+ms.date: 08/30/2022
 f1_keywords: ["C4789"]
 helpviewer_keywords: ["C4789"]
 ms.assetid: 5800c301-5afb-4af0-85c1-ceb54d775234
@@ -18,11 +18,11 @@ ms.assetid: 5800c301-5afb-4af0-85c1-ceb54d775234
 
 The warning occurs if the copy uses the intrinsic form of one of these CRT functions:
 
-- [strcpy](../../c-runtime-library/reference/strcpy-wcscpy-mbscpy.md)
+- [`strcpy`](../../c-runtime-library/reference/strcpy-wcscpy-mbscpy.md)
 
-- [memset](../../c-runtime-library/reference/memset-wmemset.md)
+- [`memset`](../../c-runtime-library/reference/memset-wmemset.md)
 
-- [memcpy](../../c-runtime-library/reference/memcpy-wmemcpy.md), [wmemcpy](../../c-runtime-library/reference/memcpy-wmemcpy.md)
+- [`memcpy`](../../c-runtime-library/reference/memcpy-wmemcpy.md), [`wmemcpy`](../../c-runtime-library/reference/memcpy-wmemcpy.md)
 
 The warning also appears when you cast a parameter to a larger data type, and then make a copy assignment from an lvalue reference.
 
@@ -35,7 +35,9 @@ Visual C++ might generate this warning for a code path that never executes. You
 #pragma warning( pop )
 ```
 
-This idiom keeps Visual C++ from generating the warning for that specific block of code. The `#pragma warning(push)` preserves the existing state before `#pragma warning(disable: 4789)` changes it. The `#pragma warning(pop)` restores the pushed state, and removes the effects of the `#pragma warning(disable:4789)`. For more information about the C++ preprocessor directive `#pragma`, see [warning](../../preprocessor/warning.md) and [Pragma Directives and the __Pragma Keyword](../../preprocessor/pragma-directives-and-the-pragma-keyword.md).
+This idiom keeps Visual C++ from generating the warning for that specific block of code. The `#pragma warning(push)` preserves the existing state before `#pragma warning(disable: 4789)` changes it. The `#pragma warning(pop)` restores the pushed state, and removes the effects of the `#pragma warning(disable:4789)`. For more information about the C++ preprocessor directive `#pragma`, see [`warning`](../../preprocessor/warning.md) and [Pragma Directives and the `__Pragma` Keyword](../../preprocessor/pragma-directives-and-the-pragma-keyword.md).
+
+The [`/sdl` (Enable Additional Security Checks)](../../build/reference/sdl-enable-additional-security-checks.md) compiler option elevates this warning to an error.
 
 ## Examples
 
 
@@ -1,7 +1,7 @@
 ---
 description: "Learn more about: Compiler warning (level 2) C4146"
 title: "Compiler warning (level 2) C4146"
-ms.date: 11/18/2021
+ms.date: 08/30/2022
 f1_keywords: ["C4146"]
 helpviewer_keywords: ["C4146"]
 ---
@@ -15,7 +15,7 @@ Unsigned types can hold only non-negative values, so unary minus (negation) usua
 
 When you express a negative integer literal, the **`-`** in front of the value is parsed as a [unary negation](../../cpp/unary-plus-and-negation-operators-plus-and.md) operator. The compiler applies the operator after it parses the numeric value. If the numeric value fits in the range of an unsigned integer type, but not the corresponding signed integer type, the compiler interprets the value as unsigned. An unsigned value is unchanged by the unary negation operator.
 
-This warning often occurs when you try to express the minimum **`int`** value, -2147483648, or the minimum **`long long`** value, -9223372036854775808. These values can't be written as -2147483648 or -9223372036854775808ll, respectively. That's because the compiler processes the expression in two stages: first, it parses the numeric value, then it applies the negation operator. For example, when the compiler parses -2147483648, it follows these steps:
+This warning often occurs when you try to express the minimum **`int`** value, -2147483648, or the minimum **`long long`** value, -9223372036854775808. These values can't be written as -2147483648 or -9223372036854775808ll, respectively. The reason is because the compiler processes the expression in two stages: first, it parses the numeric value, then it applies the negation operator. For example, when the compiler parses -2147483648, it follows these steps:
 
 1. The number 2147483648 is evaluated. Because it's greater than the maximum **`int`** value of 2147483647, but still fits in an **`unsigned int`**, the type of 2147483648 is **`unsigned int`**.
 
@@ -25,6 +25,8 @@ The unsigned type of the result can cause unexpected behavior. If the result is
 
 You can avoid C4146 by using `INT_MIN` or `LLONG_MIN` from *`<limits.h>`* or the C++ equivalent, *`<climits>`*. These values have signed types.
 
+The [`/sdl` (Enable Additional Security Checks)](../../build/reference/sdl-enable-additional-security-checks.md) compiler option elevates this warning to an error.
+
 ## Example
 
 The following sample demonstrates the unexpected behavior that can happen when the compiler generates warning C4146:
 
@@ -1,17 +1,21 @@
 ---
 description: "Learn more about: Compiler Warning (level 2) C4308"
 title: "Compiler Warning (level 2) C4308"
-ms.date: "11/04/2016"
+ms.date: 08/30/2022
 f1_keywords: ["C4308"]
 helpviewer_keywords: ["C4308"]
 ms.assetid: d4e5c53c-71b2-4bbc-8a7c-3a2a3180d9d9
 ---
 # Compiler Warning (level 2) C4308
 
-negative integral constant converted to unsigned type
+> negative integral constant converted to unsigned type
+
+## Remarks
 
 An expression converts a negative integer constant to an unsigned type. The result of the expression is probably meaningless.
 
+The [`/sdl` (Enable Additional Security Checks)](../../build/reference/sdl-enable-additional-security-checks.md) compiler option elevates this warning to an error.
+
 ## Example
 
 ```cpp
 
@@ -1,20 +1,24 @@
 ---
 description: "Learn more about: Compiler Warning (level 3) C4995"
 title: "Compiler Warning (level 3) C4995"
-ms.date: "11/04/2016"
+ms.date: 08/30/2022
 f1_keywords: ["C4995"]
 helpviewer_keywords: ["C4995"]
 ms.assetid: c6b61755-4730-4947-ad4d-d1c2bc82585a
 ---
 # Compiler Warning (level 3) C4995
 
-'function': name was marked as #pragma deprecated
+> '*function*': name was marked as `#pragma deprecated`
 
-The compiler encountered a function that was marked with pragma [deprecated](../../preprocessor/deprecated-c-cpp.md). The function may no longer be supported in a future release. You can turn this warning off with the [warning](../../preprocessor/warning.md) pragma (example below).
+## Remarks
+
+The compiler encountered a function that was marked with [`#pragma deprecated`](../../preprocessor/deprecated-c-cpp.md). The function may no longer be supported in a future release. You can turn off this warning by using [`#pragma warning`](../../preprocessor/warning.md).
+
+The [`/sdl` (Enable Additional Security Checks)](../../build/reference/sdl-enable-additional-security-checks.md) compiler option elevates this warning to an error.
 
 ## Example
 
-The following sample generates C4995:
+The following sample generates C4995. Uncomment the `#pragma warning` line to disable the warning.
 
 ```cpp
 // C4995.cpp