Merge pull request MicrosoftDocs#2302 from MicrosoftDocs/master637299144608997233

Fix git push error for protected CLA branch

Author: Colin Robertson

docs/build/reference/c-cpp-prop-page.md

@@ -1,40 +1,41 @@
 ---
 title: "CL Command Files"
-ms.date: "11/04/2016"
+description: "The MSVC compiler lets you specify command files that contain command-line options."
+ms.date: 07/08/2020
 helpviewer_keywords: ["cl.exe compiler, command files", "command files", "command files, CL compiler"]
 ms.assetid: ec3cea06-2af0-4fe9-a94c-119c9d31b3a9
 ---
 # CL Command Files
 
-A command file is a text file that contains options and filenames you would otherwise type on the [command line](compiler-command-line-syntax.md) or specify using the [CL environment variable](cl-environment-variables.md). CL accepts a compiler command file as an argument in the CL environment variable or on the command line. Unlike either the command line or the CL environment variable, a command file allows you to use multiple lines of options and filenames.
+A command file is a text file that contains compiler options and filenames. It supplies options you would otherwise type on the [command line](compiler-command-line-syntax.md), or specify using the [CL environment variable](cl-environment-variables.md). CL accepts a compiler command file as an argument, either in the CL environment variable, or on the command line. Unlike either the command line or the CL environment variable, you can use multiple lines of options and filenames in a command file.
 
-Options and filenames in a command file are processed according to the location of a command filename within the CL environment variable or on the command line. However, if the /link option appears in the command file, all options on the rest of the line are passed to the linker. Options in subsequent lines in the command file and options on the command line after the command file invocation are still accepted as compiler options. For more information on how the order of options affects their interpretation, see [Order of CL Options](order-of-cl-options.md).
+Options and filenames in a command file are processed when a command filename appears within the CL environment variable or on the command line. However, if the **`/link`** option appears in the command file, all options on the rest of the line are passed to the linker. Options in later lines in the command file, and options on the command line after the command file invocation, are still accepted as compiler options. For more information on how the order of options affects their interpretation, see [Order of CL Options](order-of-cl-options.md).
 
-A command file must not contain the CL command. Each option must begin and end on the same line; you cannot use the backslash (**\\**) to combine an option across two lines.
+A command file must not contain the CL command. Each option must begin and end on the same line; you can't use the backslash (**`\`**) to combine an option across two lines.
 
-A command file is specified by an at sign (**\@**) followed by a filename; the filename can specify an absolute or relative path.
+A command file is specified by an at sign (**`@`**) followed by a filename. The filename can specify an absolute or relative path.
 
 For example, if the following command is in a file named RESP:
 
-```
-/Og /link LIBC.LIB
+```cmd
+/Ot /link LIBC.LIB
 ```
 
 and you specify the following CL command:
 
-```
+```cmd
 CL /Ob2 @RESP MYAPP.C
 ```
 
 the command to CL is as follows:
 
-```
-CL /Ob2 /Og MYAPP.C /link LIBC.LIB
+```cmd
+CL /Ob2 /Ot MYAPP.C /link LIBC.LIB
 ```
 
-Note that the command line and the command-file commands are effectively combined.
+Here you can see how the command line and the command-file commands are effectively combined.
 
 ## See also
 
-[MSVC Compiler Command-Line Syntax](compiler-command-line-syntax.md)<br/>
-[MSVC Compiler Options](compiler-options.md)
+[MSVC compiler command-line syntax](compiler-command-line-syntax.md)<br/>
+[MSVC compiler options](compiler-options.md)

docs/build/reference/cl-command-files.md

@@ -1,33 +1,30 @@
 ---
-title: "/GT (Support Fiber-Safe Thread-Local Storage)"
-ms.date: "11/04/2016"
+title: "/GT (Support fiber-safe thread-local storage)"
+description: "The MSVC compiler option /GT enables safe optimizations for thread-local storage data."
+ms.date: 07/08/2020
 f1_keywords: ["VC.Project.VCCLCompilerTool.EnableFiberSafeOptimizations", "/gt"]
 helpviewer_keywords: ["/GT compiler option [C++]", "GT compiler option [C++]", "thread-local storage", "static thread-local storage and fiber safety", "-GT compiler option [C++]", "fiber-safe static thread-local storage compiler option [C++]"]
 ms.assetid: 071fec79-c701-432b-9970-457344133159
 ---
-# /GT (Support Fiber-Safe Thread-Local Storage)
+# `/GT` (Support fiber-safe thread-local storage)
 
 Supports fiber safety for data allocated using static thread-local storage, that is, data allocated with `__declspec(thread)`.
 
 ## Syntax
 
-```
-/GT
-```
+> **`/GT`**
 
 ## Remarks
 
 Data declared with `__declspec(thread)` is referenced through a thread-local storage (TLS) array. The TLS array is an array of addresses that the system maintains for each thread. Each address in this array gives the location of thread-local storage data.
 
-A fiber is a lightweight object that consists of a stack and a register context and can be scheduled on various threads. A fiber can run on any thread. Because a fiber may get swapped out and restarted later on a different thread, the address of the TLS array must not be cached or optimized as a common subexpression across a function call (see the [/Og (Global Optimizations)](og-global-optimizations.md) option for details). **/GT** prevents such optimizations.
+A fiber is a lightweight object that consists of a stack and a register context and can be scheduled on various threads. A fiber can run on any thread. Because a fiber may get swapped out and restarted later on a different thread, the compiler mustn't cache the address of the TLS array, or optimize it as a common subexpression across a function call. **`/GT`** prevents such optimizations.
 
 ### To set this compiler option in the Visual Studio development environment
 
 1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](../working-with-project-properties.md).
 
-1. Click the **C/C++** folder.
-
-1. Click the **Optimization** property page.
+1. Select the **Configuration Properties** > **C/C++** > **Optimization** property page.
 
 1. Modify the **Enable Fiber-safe Optimizations** property.
 
@@ -37,5 +34,5 @@ A fiber is a lightweight object that consists of a stack and a register context
 
 ## See also
 
-[MSVC Compiler Options](compiler-options.md)<br/>
-[MSVC Compiler Command-Line Syntax](compiler-command-line-syntax.md)
+[MSVC compiler options](compiler-options.md)<br/>
+[MSVC compiler command-line syntax](compiler-command-line-syntax.md)