add author metadata

TylerMSFT · TylerMSFT · commit a816923380b5 · 2021-04-06T18:00:37.000-07:00
diff --git a/docs/build/header-unit-json-reference.md b/docs/build/header-unit-json-reference.md
@@ -2,8 +2,12 @@
 description: "Reference for header-units.json file"
 title: "C++ header unit.json reference"
 ms.date: "4/13/2021"
+author: "tylermsft"
+ms.author: "twhitney"
 f1_keywords: ["header-units.json"]
 helpviewer_keywords: ["header-units.json", "header unit"]
+author: "tylermsft"
+ms.author: "twhitney"
 ---
 
 # C++ header-units.json reference
@@ -34,6 +38,7 @@ The schema also supports comments, as shown below:
         "bitset",
         // "cassert", // design is not compatible with header units
         ...
+}
 ```
 
 ## Search rules
diff --git a/docs/build/reference/headername.md b/docs/build/reference/headername.md
@@ -2,6 +2,8 @@
 title: "/headerName (Build a header unit from the specified header)"
 description: "Use the /headerName compiler option to establish a mapping between a header file and the header unit to build."
 ms.date: 04/13/2021
+author: "tylermsft"
+ms.author: "twhitney"
 f1_keywords: ["/headerName"]
 helpviewer_keywords: ["/headerName", "Use header unit IFC"]
 ---
diff --git a/docs/build/reference/headerunit.md b/docs/build/reference/headerunit.md
@@ -4,6 +4,8 @@ description: "Use the /headerUnit compiler option to associate a header file wit
 ms.date: 04/13/2021
 f1_keywords: ["/headerUnit"]
 helpviewer_keywords: ["/headerUnit", "Use header unit IFC"]
+author: "tylermsft"
+ms.author: "twhitney"
 ---
 # `/headerUnit` (Use header unit IFC)
 
@@ -41,7 +43,7 @@ The compiler can't map a single *`header-name`* to multiple IFC files. While map
 
 The compiler implicitly enables the new preprocessor when this switch is used. That is, [`/Zc:preprocessor`](zc-preprocessor.md) is added to the command line by the compiler if any form of `/headerUnit` is specified on the command line. To opt out of the implicit `/Zc:preprocessor`, specify: `/Zc:preprocessor-`
 
-If you disable the new preprocessor but a file you compile imports a header unit, the compiler will report an error.
+If you disable the new preprocessor, but a file you compile imports a header unit, the compiler will report an error.
 
 ### Examples
 
diff --git a/docs/build/reference/module-exportheader.md b/docs/build/reference/module-exportheader.md
@@ -2,6 +2,8 @@
 title: "/exportHeader (Create header units)"
 description: "Use the /exportHeader compiler option to create module header units for the header-name or include files specified."
 ms.date: 04/13/2020
+author: "tylermsft"
+ms.author: "twhitney"
 f1_keywords: ["/exportHeader"]
 helpviewer_keywords: ["/exportHeader", "Create header units"]
 ---
@@ -33,7 +35,7 @@ By default, the compiler doesn't produce an object file when a header unit is co
 
 You may find it helpful to use the complementary option **`/showResolvedHeader`**. The **`/showResolvedHeader`** option prints an absolute path to the file the *`header-name`* argument resolves to.
 
-**`/exportHeader`** can handle multiple inputs at once even under **`/MP`**. We recommended you use **`/ifcOutput  <directory>`** to create a separate *`.ifc`* file for each compilation.
+**`/exportHeader`** can handle multiple inputs at once, even under **`/MP`**. We recommended you use **`/ifcOutput  <directory>`** to create a separate *`.ifc`* file for each compilation.
 
 ### Examples
 
diff --git a/docs/build/reference/sourcedependencies-directives.md b/docs/build/reference/sourcedependencies-directives.md
@@ -2,6 +2,8 @@
 title: "/sourceDependencies:directives (Report source-level dependencies and use an allowlist)"
 description: "Reference guide to the /sourceDependencies:directives compiler option in Microsoft C++."
 ms.date: 04/13/2020
+author: "tylermsft"
+ms.author: "twhitney"
 f1_keywords: ["/sourceDependencies:directives"]
 helpviewer_keywords: ["/sourceDependencies:directives compiler option", "/sourceDependencies:directives"]
 ---
@@ -13,17 +15,17 @@ This command-line option is similar to [`/sourceDependencies`](sourcedependencie
 
 - Unlike `/sourceDependencies`, the compiler doesn't produce compiled output. Instead, the files are scanned for module directives, but no compiled code, modules, or header units are produced.
 - Unlike `/sourceDependencies`, the output JSON file doesn't list imported modules and imported header units (`.ifc` files) because this switch does a scan of the project files, not a compilation, so there are no built modules or header units to import.
-- `/sourceDependencies:directives`is designed to be used before `.ifc` files are built.
+- `/sourceDependencies:directives`is designed to be used before *`.ifc`* files are built.
 
 ## Syntax
 
 > **`/sourceDependencies:directives[-]`** *filename*\
-> **`/sourceDependencies:directives[-]`** *directory*\
+> **`/sourceDependencies:directives[-]`** *directory*
 
 ## Arguments
 
 *`-`*\
-If the single dash is provided, then the compiler will emit the source dependencies JSON to `stdout` or where the compiler output is redirected to.
+If the single dash is provided, then the compiler will emit the source dependencies JSON to `stdout`, or to where compiler output is redirected to.
 
 *`filename`*\
 The compiler writes the source dependency output to the specified filename, which may include a relative or absolute path.\
diff --git a/docs/build/reference/sourcedependencies.md b/docs/build/reference/sourcedependencies.md
@@ -2,6 +2,8 @@
 title: "/sourceDependencies (Report source-level dependencies)"
 description: "Reference guide to the /sourceDependencies compiler option in Microsoft C++."
 ms.date: 04/13/2020
+author: "tylermsft"
+ms.author: "twhitney"
 f1_keywords: ["/sourceDependencies"]
 helpviewer_keywords: ["/sourceDependencies compiler option", "/sourceDependencies"]
 ---
@@ -11,7 +13,7 @@ This command-line switch generates a JSON file that details the source-level dep
 
 - Header files (both transitive and directly included headers).
 - The PCH used (if **`/Yu`** is specified).
-- Imported modules and imported header units (both transitive and directly imported modules/header units).
+- Imported modules and imported header units (both transitive and directly imported module/header units).
 
 ## Syntax
 
@@ -21,7 +23,7 @@ This command-line switch generates a JSON file that details the source-level dep
 ## Arguments
 
 *`-`*\
-If the single dash is provided, then the compiler will emit the source dependencies JSON to `stdout` or where the compiler output is redirected to.
+If the single dash is provided, then the compiler will emit the source dependencies JSON to `stdout`, or to where compiler output is redirected to.
 
 *`filename`*\
 The compiler writes the source dependency output to the specified filename, which may include a relative or absolute path.\
diff --git a/docs/build/walkthrough-header-units.md b/docs/build/walkthrough-header-units.md
@@ -3,6 +3,8 @@ description: "Learn more about C++ header units by converting a header file to a
 title: "Walkthrough: Build and import header units in Microsoft Visual C++ projects"
 ms.date: "4/13/2021"
 ms.custom: "conceptual"
+author: "tylermsft"
+ms.author: "twhitney"
 helpviewer_keywords: ["import", "header unit", "ifc", "stl"]
 ---
 
