update text

Author: ghogen

docs/msbuild/errors/msb3025.md

@@ -43,7 +43,7 @@ This error occurs when the [Copy task](../copy-task.md) is provided a path to a
 
 If you control the build logic where the `Copy` task is used, check your logic that creates the inputs for the `SourceFiles` parameter to see whether the paths you're providing are the ones you intended. If your intention is to copy the contents of a directory, the `SourceFiles` parameter of the `Copy` task should be an item that includes the files in the directory.
 
-This can also occur if a folder structure changes and what was a path to a file is now a path to a folder. Update path inputs such as environment variables, command lines, and MSBuild properties to account for the new folder structure.
+This situation can easily occur in a build system if the folder structure changes and what was a path to a file is now a path to a folder. Update path inputs such as environment variables, command lines, and MSBuild properties to account for the new folder structure.
 
 <!-- :::editable-content-end::: -->
 <!-- :::ErrorDefinitionDescription-end::: -->

docs/msbuild/errors/msb3088.md

@@ -37,15 +37,15 @@ This article describes the MSB3088 error code.
 -->
 ## Description
 
-MSBuild uses certain files called state files to cache information between one build session and another. This information is used to avoid repeating analysis done in a previous run, and therebty improve performance. For example, information about referenced assemblies is reused when referenced assemblies haven't changed between builds to avoid having to repeat the same dependency analysis each time you build.
+MSBuild uses certain files called state files to cache information between one build session and another. This information is used to avoid repeating analysis done in a previous run, and thereby improve performance. For example, information about referenced assemblies is reused when referenced assemblies haven't changed between builds to avoid having to repeat the same dependency analysis each time you build.
 
-This message is shown when a one of the state files couldn't be read, for any reason. It may be followed by a message from the operating system that gives more information about what the error was.
+This message is shown when a one of the state files couldn't be read, for any reason. It may be followed by a message from the operating system that gives more information about what the problem was.
 
 ## Resolution
 
-This isn't an error, so your project still builds even if this message is shown. However, it might mean builds could be faster if the root of the problem is found and fixed.
+This condition doesn't blocks the build, since MSBuild simply repeats the analysis that was cached, so your project still builds even if this message appears. However, it might mean builds could be faster if the root of the problem is found and fixed.
 
-Look to the error message from the operating system to understand what the root cause of the problem is and get ideas on how to address it. 
+Look to the error message from the operating system to understand what the root cause of the problem is and how to fix it.
 <!-- :::editable-content-end::: -->
 <!-- :::ErrorDefinitionDescription-end::: -->
 

docs/msbuild/errors/msb3107.md

@@ -37,7 +37,7 @@ This article describes the MSB3107 error code.
 -->
 ## Description
 
-This error occurs when there's a problem with a `ProjectReference` in a project file. A `ProjectReference` element in MSBuild indicates a dependency on another project in the solution, for example, when you reference a class library project in a project that uses the library. In C# code, you can often look for the `using` directives in the project to see how it depends on APIs defined in the other project. The following code example shows a `ProjectReference` element that references `ClassLibrary1`.
+This error occurs when there's a problem with a `ProjectReference` in a project file. A `ProjectReference` element in MSBuild indicates a dependency on another project in the solution, for example, when you reference a class library project in a project that uses the library. In C# code, you can often look for the `using` directives in the project to see how it depends on APIs defined in the other project. The following code example shows a `ProjectReference` element that references `Calculator.Library`.
 
 ```xml
   <ItemGroup>

docs/msbuild/errors/msb4075.md

@@ -37,11 +37,11 @@ This article describes the MSB4075 error code.
 -->
 ## Description
 
-This error is given when MSBuild tries to open a project file that is in a format is no longer supported in later versions of Visual Studio and MSBuild. For example, projects with the extension `.vcproj` are not supported.
+This error is given when MSBuild tries to open a project file that is in a format is no longer supported in the current version of Visual Studio and MSBuild. For example, projects with the extension `.vcproj` are not supported in MSBuild.
 
 ## Resolution
 
-Open the project in Visual Studio to convert the project to a newer format. For example, in the case of `.vcproj`, Visual Studio generates a `.vcxproj` file, which you can build on the MSBuild command line, or in Visual Studio.
+Open the project in Visual Studio to convert the project to a newer format. For example, in the case of `.vcproj`, Visual Studio upgrades the project and generates a `.vcxproj` file, which you can build on the MSBuild command line, or in Visual Studio.
 
 <!-- :::editable-content-end::: -->
 <!-- :::ErrorDefinitionDescription-end::: -->

docs/msbuild/errors/msb4244.md

@@ -37,11 +37,11 @@ This article describes the MSB4244 error code.
 -->
 ## Description
 
-An SDK resolver assembly is an assembly that is loaded when an SDK is referenced in a project file. The purpose of the resolve assembly is to find and load the appropriate SDK. If this error occurs, it means that the resolver assembly couldn't be located.
+An SDK resolver assembly is an assembly that is loaded when an SDK is referenced in a project file. The purpose of the SDK resolver is to find and load the appropriate SDK. If this error occurs, it means that the resolver assembly couldn't be located or loaded.
 
 ## Resolution
 
-This error should never occur if you're using `dotnet build` or Visual Studio to run MSBuild, but it could occur in a custom tool that uses the MSBuild API to perform a build and doesn't locate the right MSBuild installation files. The recommended way to locate MSBuild is to use <xref:Microsoft.Build.Locator.MSBuildLocator>. For detailed instructions, see [Find and use MSBuild versions](../find-and-use-msbuild-versions.md).
+This error should never occur if you're using `dotnet build` or Visual Studio to build, but it could occur in a custom tool that uses the MSBuild API to perform a build and doesn't locate the right MSBuild installation files. The recommended way to locate MSBuild is to use <xref:Microsoft.Build.Locator.MSBuildLocator>. For detailed instructions, see [Find and use MSBuild versions](../find-and-use-msbuild-versions.md).
 
 <!-- :::editable-content-end::: -->
 <!-- :::ErrorDefinitionDescription-end::: -->