acrolinx

Author: TylerMSFT

docs/build/reference/sourcedependencies-directives.md

@@ -9,7 +9,7 @@ helpviewer_keywords: ["/sourceDependencies:directives compiler option", "/source
 ---
 # `/sourceDependencies:directives` (List module and header unit dependencies)
 
-This command-line option scans source files and their `#include` statements to generate a JSON file that lists module export and imports. This information can be used by a build system to determine the build order of modules and header units.
+This command-line option scans source files and their `#include` statements to generate a JSON file that lists module export and imports. A build system can use this information to determine the build order of modules and header units.
 
 This option differs from [`/sourceDependencies`](sourcedependencies.md) in the following ways:
 
@@ -99,7 +99,7 @@ No *`.ifc`* files are listed in the output because they weren't built. Unlike `/
 
 ## To set this compiler option in Visual Studio
 
-You normally shouldn't set this option yourself in the Visual Studio development environment. It's set by the build system.
+You normally shouldn't set this option yourself in the Visual Studio development environment. The build system sets it.
 
 ## See also
 

docs/cpp/modules-cpp.md

@@ -106,7 +106,7 @@ The **`export`** keyword is only used in interface files. An implementation file
 
 The rules for namespaces in modules are the same as any other code. If a declaration within a namespace is exported, the enclosing namespace (excluding members that aren't explicitly exported in that namespace) is also implicitly exported. If a namespace is explicitly exported, all declarations within that namespace definition are exported.
 
-When the compiler does argument-dependent lookup for overload resolutions in the importing translation unit, it considers functions declared in the same translation unit (including module interfaces) as where the type of the function's arguments are defined.
+When the compiler does argument-dependent lookup for overload resolution in the importing translation unit, it considers functions declared in the same translation unit (including module interfaces) as where the type of the function's arguments is defined.
 
 ### Module partitions