Apply suggestions from code review

Co-authored-by: Ben Villalobos <[email protected]>

Author: ghogen

docs/msbuild/customize-your-build.md

@@ -192,9 +192,9 @@ If you need different behaviors depending on the .NET language (C#, Visual Basic
 
 ## Handle generated files
 
-In any given build, files that get generated during the build behave differently from static files (such as source files). For this reason, it's important to understand [How MSBuild Builds Projects](build-process-overview.md). Two of the phases are [evaluation phase](build-process-overview.md#evaluation-phase) (MSBuild reads your project, imports everything, creates properties, expands globs for items outside of targets, and sets up the build process), and the [execution phase](build-process-overview.md#execution-phase) (MSBuild runs targets and tasks with the provided properties and items in order to perform the build).
+In any given build, files that get generated during the build behave differently from static files (such as source files). For this reason, it's important to understand [How MSBuild Builds Projects](build-process-overview.md). The two phases are [Evaluation phase](build-process-overview.md#evaluation-phase) and [Execution phase](build-process-overview.md#execution-phase). During Evaluation, MSBuild reads your project, imports everything, creates properties, expands globs for items, and sets up the build process. During Execution, MSBuild performs the build by running targets and tasks with the data it parsed during Evaluation.
 
-Files generated during execution don't exist during evaluation, therefore they aren't included in the build process. To solve this problem, manually add generated files into the build process. The recommended way to do this is by adding the new file to the `Content` or `None` items before the `BeforeBuild` target, as in the following example:
+Files generated during execution don't exist during evaluation, therefore they aren't included in the build process. To solve this problem, you must manually add the generated files into the build process. The recommended way to do this is by adding the new file to the `Content` or `None` items before the `BeforeBuild` target, as in the following example:
 
 ```xml
 <Target Name="MyTarget" BeforeTargets="BeforeBuild">
@@ -208,7 +208,7 @@ Files generated during execution don't exist during evaluation, therefore they a
 </Target>
 ```
 
-Adding your generated file to `None` or `Content` is sufficient for the build process to see it. You also want to ensure it gets added at the right time. Ideally, your target runs before `BeforeBuild`. `AssignTargetPaths` is another option, as it is the final opportunity to run before `None` and `Content` items (among others) are transformed into new items. See [Common Item Types](common-msbuild-project-items.md).
+Adding your generated file to `None` or `Content` is sufficient for the build process to see it. You also want to ensure it gets added at the right time. Ideally, your target runs before `BeforeBuild`. `AssignTargetPaths` is another possible target, as it is the final opportunity to modify `None` and `Content` items (among others) before they are transformed into new items. See [Common Item Types](common-msbuild-project-items.md).
 
 ## Customize the solution build