edits

Author: GitHubber17

docs/msbuild/errors/msb3721.md

@@ -30,7 +30,7 @@ This error occurs when a command launched in the build process exits with a nonz
 
 ## Resolution
 
-To investigate the error, check the build output or build log to see if the custom build step produced an error with information about the problem. If not, try running the step separately to check for any problems or unexpected behavior.
+Check the build output or build log to see if the custom build step produced an error with information about the problem. If not, try running the step separately to check for any problems or unexpected behavior.
 
 If you can't see the exact command-line that failed, you can change the verbosity of the build output to show more detail.
 

docs/msbuild/errors/msb3971.md

@@ -16,13 +16,13 @@ ms.author: ghogen
 manager: mijacobs
 ms.subservice: msbuild
 ---
-# MSB3971 diagnostic code
+# MSB3971
 
 This article describes the MSB3971 error code.
 
 ## Message text
 
-`The reference assemblies for 'framework-version' were not found. You might be using an older .NET SDK to target .NET 5.0 or higher. Update Visual Studio and/or your .NET SDK.`
+`MSB3971: The reference assemblies for 'framework-version' were not found. You might be using an older .NET SDK to target .NET 5.0 or higher. Update Visual Studio and/or your .NET SDK.`
 
 ## Description
 

docs/msbuild/errors/msb4018.md

@@ -28,7 +28,7 @@ This article describes the MSB4018 error code.
 
 This error is emitted when a task fails with an unhandled exception. This issue is generally a sign of a bug in the task.
 
-You might encounter this error, if the build runs a task in an environment for which it wasn't prepared. For example, when a task has an x86 dependency, but the task runs in a 64-bit MSBuild environment. This scenario can manifest as a `System.DllNotFoundException` exception, as shown in the following output:
+You might encounter this error when the build runs a task in an environment for which it wasn't prepared. For example, when a task has an x86 dependency, but the task runs in a 64-bit MSBuild environment. This scenario can manifest as a `System.DllNotFoundException` exception, as shown in the following output:
 
 ```output
 S:\BitnessInMSBuild\ShowErrors.proj(6,7): error MSB4018: The "AnyCPUTaskWithPInvoke" task failed unexpectedly.