edits

Author: GitHubber17

docs/msbuild/errors/msb3277.md

@@ -26,15 +26,15 @@ This article describes the MSB3277 error code.
 
 ## Description
 
-This error occurs during a build when more than one version of the same dependent assembly is referenced in a build of the same project. In a .NET build, all assemblies that are referenced, directly or indirectly through other referenced assemblies, have to resolve to the same version. You can't reference two different and conflicting versions of the same assembly when building the same binary. The error is emitted by the [ResolveAssemblyReference task](../resolveassemblyreference-task.md), which looks at all the referenced assemblies, and all assemblies referenced indirectly by those assemblies, and so on, until all assembly references are resolved.
+This error occurs during a build when more than one version of the same dependent assembly is referenced in a build of the same project. In a .NET build, all assemblies that are referenced, directly or indirectly through other referenced assemblies, have to resolve to the same version. You can't reference two different and conflicting versions of the same assembly when building the same binary. The [ResolveAssemblyReference task](../resolveassemblyreference-task.md) emits this error. The task inspects all the referenced assemblies, and all assemblies referenced indirectly by those assemblies, and so on. The task works through the process until all assembly references are resolved.
 
 ## Diagnose the error
 
 To diagnose the error, first enable diagnostic log output by using the `-verbosity:diag` command-line switch, and then check the MSBuild log file with the full diagnostics output. For longer output logs on large projects, consider using the binary log `-bl` command-line switch and the [MSBuild Structured Log Viewer](https://msbuildlog.com/) to view the output more easily.
 
-In MSBuild 16.x or later, the specific assembly versions in conflict are written to the log file. In earlier versions of MSBuild, the content isn't added to the log file. Instead, follow the assembly dependency chain to locate the conflicting reference. Look at each assembly that your project references, and then the assemblies that the initial assemblies reference, and so on. Follow this process until you identify the conflicting assembly version(s).
+In MSBuild 16.x or later, the specific assembly versions in conflict are written to the log file. In earlier versions of MSBuild, the content isn't added to the log file. Instead, follow the assembly dependency chain to locate the conflicting reference. Look at each assembly that your project references, and then the assemblies that the initial assemblies reference, and so on. Follow this process until you identify the conflicting assembly versions.
 
-The diagnostics log should identify the specific assembly version(s) that are in conflict and the reason for the conflict(s). For example, a reference to *assembly1.dll*, which references *assembly2.dll* version **x**, but also references *assembly2.dll* version **y**. MSBuild can't determine which version to use for the assembly.
+The diagnostics log should identify the specific assembly versions that are in conflict and the reasons for the conflicts. For example, a reference to *assembly1.dll*, which references *assembly2.dll* version **x**, but also references *assembly2.dll* version **y**. MSBuild can't determine which version to use for the assembly.
 
 The following example is an excerpt from a diagnostic log showing a conflict between two versions of `StreamJsonRpc`:
 
@@ -84,11 +84,11 @@ How you resolve this issue depends on your project configuration and assembly de
 
 - Update the version of an assembly on disk by upgrading or reinstalling a NuGet package or SDK.
 - Update all packages to the latest versions with the `Update-Package -reinstall` command in the Package Manager Console for Visual Studio. For more information, see [Reinstalling and updating packages](/nuget/consume-packages/reinstalling-and-updating-packages).
-- For projects with multiple versions of a referenced assembly on disk, update the projec or the dependencies to reference the latest version of the installed conflicting assembly. The Global Assembly Cache (GAC) might also be a source of a potential conflict, in cases where you reference a specific version of an assembly, but the GAC overrides it. For more information, see [Global Assembly Cache](/dotnet/framework/app-domains/gac).
+- For projects with multiple versions of a referenced assembly on disk, update the project or the dependencies to reference the latest version of the installed conflicting assembly. The Global Assembly Cache (GAC) might also be a source of a potential conflict, in cases where you reference a specific version of an assembly, but the GAC overrides it. For more information, see [Global Assembly Cache](/dotnet/framework/app-domains/gac).
 
 ## External components
 
-If the conflict is in a non-Microsoft component, the component might not be supported with the version of the conflicting assembly you're using in your project. Look to the provider of the other component to see if they offer an updated, compatible version. If a fix isn't available, the solution might be to downgrade the version of the conflicting assembly you're referencing to match the version that the other component uses.
+If the conflict is in a non-Microsoft component, the component might not be supported with the version of the conflicting assembly you're using in your project. Check the provider of the other component to see if they offer an updated, compatible version. If a fix isn't available, the solution might be to downgrade the version of the conflicting assembly you're referencing to match the version that the other component uses.
 
 ## Binding redirects
 

docs/msbuild/errors/msb3305.md

@@ -43,10 +43,7 @@ As a temporary measure, you can silence the warning by adding the following valu
 ```
 
 > [!WARNING]
-> As you work to resolve this MSBuild error, avoid some common techniques that can cause you to miss vital information:
->
-> - Suppression of MSBuild diagnostic information
-> - Use of the `ResolveComReferenceSilent` property to hide the MSB3305 warning
+> We don't recommend suppressing MSBuild diagnostic information. Eliminating the warning doesn't address the underlying problem. Using the ResolveComReferenceSilent property to hide the warning might also hide other COM reference warnings you don't intend to suppress.
 
 For more information, see [Add references to type libraries](/dotnet/framework/interop/how-to-add-references-to-type-libraries).