Merge branch 'ifcmap' of https://github.com/TylerMSFT/cpp-docs-pr into ifcmap

Author: TylerMSFT

docs/cpp/modules-cpp.md

@@ -111,7 +111,7 @@ The `import` declaration can appear only at global scope.
 
 A *module interface* exports the module name and all the namespaces, types, functions, and so on that make up the public interface of the module. A *module implementation* defines the things exported by the module. In its simplest form, a module can consist of a single file that combines the module interface and implementation. You can also put the implementations in one or more separate module implementation files, similar to how *`.h`* and *`.cpp`* files are used.
 
-For larger modules, you can split parts of the module into submodules called *partitions*. Each partition consists of a module interface file that exports a module partition name. A partition may also have one or more partition implementation files. The module as a whole has one *primary module interface*, the public interface of the module that may also import and export the partition interfaces.
+For larger modules, you can split parts of the module into submodules called *partitions*. Each partition consists of a module interface file that exports a module partition name. A partition might also have one or more partition implementation files. The module as a whole has one *primary module interface*, the public interface of the module that might also import and export the partition interfaces.
 
 A module consists of one or more *module units*. A module unit is a translation unit (a source file) that contains a module declaration. There are several types of module units:
 
@@ -203,4 +203,4 @@ import "myheader.h";
 
 [`module`, `import`, `export`](import-export-module.md)\
 [Named modules tutorial](tutorial-named-modules-cpp.md)\
-[Compare header units, modules, and precompiled headers](../build/compare-inclusion-methods.md)
+[Compare header units, modules, and precompiled headers](../build/compare-inclusion-methods.md)