Fix more __try keywords

Colin Robertson · Colin Robertson · commit e04f2b9b7d88 · 2020-08-25T03:48:38.000-07:00
diff --git a/docs/build/exception-handling-x64.md b/docs/build/exception-handling-x64.md
@@ -297,7 +297,7 @@ typedef struct _DISPATCHER_CONTEXT {
 } DISPATCHER_CONTEXT, *PDISPATCHER_CONTEXT;
 ```
 
-**ControlPc** is the value of RIP within this function. This value is either an exception address or the address at which control left the establishing function. The RIP is used to determine if control is within some guarded construct inside this function, for example, a `__try` block for `__try`/**`__except`** or `__try`/**`__finally`**.
+**ControlPc** is the value of RIP within this function. This value is either an exception address or the address at which control left the establishing function. The RIP is used to determine if control is within some guarded construct inside this function, for example, a **`__try`** block for **`__try`**/**`__except`** or **`__try`**/**`__finally`**.
 
 **ImageBase** is the image base (load address) of the module containing this function, to be added to the 32-bit offsets used in the function entry and unwind info to record relative addresses.
 
diff --git a/docs/dotnet/exceptions-in-cpp-cli.md b/docs/dotnet/exceptions-in-cpp-cli.md
@@ -14,6 +14,6 @@ The articles in this section of the documentation explain exception handling in
 |[Basic Concepts in Using Managed Exceptions](../dotnet/basic-concepts-in-using-managed-exceptions.md)|Discusses exception handling in managed applications.|
 |[Differences in Exception Handling Behavior Under /CLR](../dotnet/differences-in-exception-handling-behavior-under-clr.md)|Discusses the differences between standard exception handling and exception handling in C++/CLI.|
 |[finally](../dotnet/finally.md)|Describes the **`finally`** block that's used to clean up resources that are left after an exception occurs.|
-|[How to: Catch Exceptions in Native Code Thrown from MSIL](../dotnet/how-to-catch-exceptions-in-native-code-thrown-from-msil.md)|Demonstrates how to use `__try` and **`__except`** to catch exceptions in native code that are thrown from MSIL.|
+|[How to: Catch Exceptions in Native Code Thrown from MSIL](../dotnet/how-to-catch-exceptions-in-native-code-thrown-from-msil.md)|Demonstrates how to use **`__try`** and **`__except`** to catch exceptions in native code that are thrown from MSIL.|
 |[How to: Define and Install a Global Exception Handler](../dotnet/how-to-define-and-install-a-global-exception-handler.md)|Demonstrates how to capture unhandled exceptions.|
 |[.NET Programming with C++/CLI (Visual C++)](../dotnet/dotnet-programming-with-cpp-cli-visual-cpp.md)|The top-level article for .NET programming in the Visual C++ documentation.|
diff --git a/docs/dotnet/how-to-catch-exceptions-in-native-code-thrown-from-msil.md b/docs/dotnet/how-to-catch-exceptions-in-native-code-thrown-from-msil.md
@@ -6,7 +6,7 @@ ms.assetid: c15afd2b-8505-43bf-8a4a-f1d41532a124
 ---
 # How to: Catch Exceptions in Native Code Thrown from MSIL
 
-In native code, you can catch native C++ exception from MSIL.  You can catch CLR exceptions with `__try` and **`__except`**.
+In native code, you can catch native C++ exception from MSIL.  You can catch CLR exceptions with **`__try`** and **`__except`**.
 
 For more information, see [Structured Exception Handling (C/C++)](../cpp/structured-exception-handling-c-cpp.md) and [Modern C++ best practices for exceptions and error handling](../cpp/errors-and-exception-handling-modern-cpp.md).
 
diff --git a/docs/error-messages/compiler-errors-2/compiler-error-c2702.md b/docs/error-messages/compiler-errors-2/compiler-error-c2702.md
@@ -1,15 +1,16 @@
 ---
 title: "Compiler Error C2702"
-ms.date: "11/04/2016"
+description: "Describes Microsoft C/C++ compiler error C2702."
+ms.date: 08/25/2020
 f1_keywords: ["C2702"]
 helpviewer_keywords: ["C2702"]
 ms.assetid: 6def15d4-9a8d-43e7-ae35-42d7cb57c27e
 ---
 # Compiler Error C2702
 
-__except may not appear in termination block
+> `__except` may not appear in termination block
 
-An exception handler (`__try`/**`__except`**) cannot be nested inside a **`__finally`** block.
+An exception handler (**`__try`**/**`__except`**) cannot be nested inside a **`__finally`** block.
 
 The following sample generates C2702:
 
diff --git a/docs/error-messages/compiler-errors-2/compiler-error-c2705.md b/docs/error-messages/compiler-errors-2/compiler-error-c2705.md
@@ -9,7 +9,7 @@ ms.assetid: 29249ea3-4ea7-4105-944b-bdb83e8d6852
 
 'label' : illegal jump into 'exception handler block' scope
 
-Execution jumps to a label within a **`try`**/**`catch`**, `__try`/**`__except`**, `__try`/**`__finally`** block. For more information, see [Exception Handling](../../cpp/exception-handling-in-visual-cpp.md).
+Execution jumps to a label within a **`try`**/**`catch`**, **`__try`**/**`__except`**, **`__try`**/**`__finally`** block. For more information, see [Exception Handling](../../cpp/exception-handling-in-visual-cpp.md).
 
 The following sample generates C2705:
 
diff --git a/docs/error-messages/compiler-errors-2/compiler-error-c2706.md b/docs/error-messages/compiler-errors-2/compiler-error-c2706.md
@@ -1,15 +1,16 @@
 ---
 title: "Compiler Error C2706"
-ms.date: "11/04/2016"
+description: "Describes Microsoft C/C++ compiler error C2706."
+ms.date: 08/25/2020
 f1_keywords: ["C2706"]
 helpviewer_keywords: ["C2706"]
 ms.assetid: e18da924-c42d-4b09-8e29-f4e0382d7dc6
 ---
 # Compiler Error C2706
 
-illegal __except without matching \__try (missing '}' in \__try block?)
+> illegal `__except` without matching `__try` (missing '}' in `__try` block?)
 
-The compiler did not find a closing brace for a `__try` block.
+The compiler did not find a closing brace for a **`__try`** block.
 
 The following sample generates C2706:
 
diff --git a/docs/error-messages/compiler-errors-2/compiler-error-c2712.md b/docs/error-messages/compiler-errors-2/compiler-error-c2712.md
@@ -1,17 +1,18 @@
 ---
 title: "Compiler Error C2712"
-ms.date: "11/04/2016"
+description: "Describes Microsoft C/C++ compiler error C2712."
+ms.date: 08/25/2020
 f1_keywords: ["C2712"]
 helpviewer_keywords: ["C2712"]
 ms.assetid: f7d4ffcc-7ed2-459b-8067-a728ce647071
 ---
 # Compiler Error C2712
 
-> cannot use __try in functions that require object unwinding
+> cannot use `__try` in functions that require object unwinding
 
 ## Remarks
 
-Error C2712 can occur if you use [/EHsc](../../build/reference/eh-exception-handling-model.md), and a function with structured exception handling also has objects that require unwinding (destruction).
+Error C2712 can occur if you use [`/EHsc`](../../build/reference/eh-exception-handling-model.md), and a function with structured exception handling also has objects that require unwinding (destruction).
 
 Possible solutions:
 
@@ -21,11 +22,11 @@ Possible solutions:
 
 - Compile without /EHsc
 
-Error C2712 can also occur if you call a method declared by using the [__event](../../cpp/event.md) keyword. Because the event might be used in a multithreaded environment, the compiler generates code that prevents manipulation of the underlying event object, and then encloses the generated code in an SEH [try-finally statement](../../cpp/try-finally-statement.md). Consequently, error C2712 will occur if you call the event method and pass by value an argument whose type has a destructor. One solution in this case is to pass the argument as a constant reference.
+Error C2712 can also occur if you call a method declared by using the [`__event`](../../cpp/event.md) keyword. Because the event might be used in a multithreaded environment, the compiler generates code that prevents manipulation of the underlying event object, and then encloses the generated code in an SEH [`try-finally` statement](../../cpp/try-finally-statement.md). Consequently, error C2712 will occur if you call the event method and pass by value an argument whose type has a destructor. One solution in this case is to pass the argument as a constant reference.
 
-C2712 can also occur if you compile with **/clr:pure** and declare a static array of pointers-to-functions in a `__try` block. A static member requires the compiler to use dynamic initialization under **/clr:pure**, which implies C++ exception handling. However, C++ exception handling is not allowed in a `__try` block.
+C2712 can also occur if you compile with **`/clr:pure`** and declare a static array of pointers-to-functions in a **`__try`** block. A static member requires the compiler to use dynamic initialization under **`/clr:pure`**, which implies C++ exception handling. However, C++ exception handling is not allowed in a **`__try`** block.
 
-The **/clr:pure** and **/clr:safe** compiler options are deprecated in Visual Studio 2015 and unsupported in Visual Studio 2017.
+The **`/clr:pure`** and **`/clr:safe`** compiler options are deprecated in Visual Studio 2015 and unsupported in Visual Studio 2017.
 
 ## Example
 
diff --git a/docs/error-messages/compiler-errors-2/compiler-error-c2713.md b/docs/error-messages/compiler-errors-2/compiler-error-c2713.md
@@ -1,12 +1,13 @@
 ---
 title: "Compiler Error C2713"
-ms.date: "11/04/2016"
+description: "Describes Microsoft C/C++ compiler error C2713."
+ms.date: 08/25/2020
 f1_keywords: ["C2713"]
 helpviewer_keywords: ["C2713"]
 ms.assetid: bae9bee3-b4b8-4be5-b6a5-02df587a7278
 ---
 # Compiler Error C2713
 
-only one form of exception handling permitted per function
+> only one form of exception handling permitted per function
 
-You cannot use structured exception handling (`__try`/**`__except`**) and C++ exception handling (**`try`**/**`catch`**) in the same function.
+You can't use structured exception handling (**`__try`**/**`__except`**) and C++ exception handling (**`try`**/**`catch`**) in the same function.
diff --git a/docs/error-messages/compiler-warnings/compiler-warning-level-4-c4932.md b/docs/error-messages/compiler-warnings/compiler-warning-level-4-c4932.md
@@ -1,15 +1,16 @@
 ---
 title: "Compiler Warning (level 4) C4932"
-ms.date: "11/04/2016"
+description: "Describes Microsoft C/C++ compiler warning C4932."
+ms.date: 08/25/2020
 f1_keywords: ["C4932"]
 helpviewer_keywords: ["C4932"]
 ms.assetid: 0b8d88cc-21f6-45cb-a9f5-1795b7db0dfa
 ---
 # Compiler Warning (level 4) C4932
 
-__identifier(identifier) and \__identifier(identifier) are indistinguishable
+> `__identifier(identifier_1)` and `__identifier(identifier_2)` are indistinguishable
 
-The compiler is unable to distinguish between **_finally** and **`__finally`** or `__try` and **_try** as a parameter passed to [__identifier](../../extensions/identifier-cpp-cli.md). You should not attempt to use them both as identifiers in the same program, as it will result in a [C2374](../../error-messages/compiler-errors-1/compiler-error-c2374.md) error.
+The compiler is unable to distinguish between **`_finally`** and **`__finally`** or **`__try`** and **`_try`** as a parameter passed to [`__identifier`](../../extensions/identifier-cpp-cli.md). You should not attempt to use them both as identifiers in the same program, as it will result in a [C2374](../../error-messages/compiler-errors-1/compiler-error-c2374.md) error.
 
 The following sample generates C4932:
 
