update bookmark links

Author: GitHubber17

docs/ide/dotfuscator/index.md

@@ -383,7 +383,7 @@ See [the full Dotfuscator Community User Guide at preemptive.com][full] for deta
 [attributes-checks]: https://www.preemptive.com/dotfuscator/ce/docs/help/attributes_checks.html
 [attributes-obfuscation]: https://www.preemptive.com/dotfuscator/ce/docs/help/attributes_obfuscation.html
 
-[verbosity]: ../how-to-view-save-and-configure-build-log-files.md#to-change-the-amount-of-information-included-in-the-build-log
+[verbosity]: ../how-to-view-save-and-configure-build-log-files.md#specify-data-verbosity-for-build-logs
 [dotnet-attributes]: /dotnet/standard/attributes
 [application-insights]: /azure/azure-monitor/app/app-insights-overview
 [nuget-org]: https://www.nuget.org/

docs/ide/how-to-view-save-and-configure-build-log-files.md

@@ -1,7 +1,7 @@
 ---
 title: View, save, and configure build log files
 description: Explore how to configure build log files with information about the compiler and other tools for troubleshooting build failures.
-ms.date: 08/20/2024
+ms.date: 08/21/2024
 ms.subservice: compile-build
 ms.topic: how-to
 author: ghogen
@@ -45,8 +45,6 @@ Use the following procedures to generate and view build log files for your scena
 
    You can generate build logs by running MSBuild directly from the command line by using the `-fileLogger` (`-fl`) command-line option. For more information, see [Obtain build logs with MSBuild](../msbuild/obtaining-build-logs-with-msbuild.md).
 
-<a name="to-change-the-amount-of-information-included-in-the-build-log"></a>
-
 ## Specify data verbosity for build logs
 
 You can specify how much information to include in the build log files. The amount of data in the log file columns is measured as *logger verbosity*. The number of log file rows represent *messages collected*. The log verbosity (column values) affects the types of logged messages (row values). **Quiet** verbosity produces minimal logging in the build output. **Diagnostic** is the most verbose setting and generates log files with all possible data.

docs/msbuild/errors/msb3721.md

@@ -26,4 +26,4 @@ If you can't see the exact command-line that failed, you can change the verbosit
 
 You can also set the `MSBuildDebugEngine` environment variable to 1 to get all possible logs. See [Building MSBuild for the .NET Framework - Logs](https://github.com/dotnet/msbuild/blob/main/documentation/wiki/Building-Testing-and-Debugging-on-Full-Framework-MSBuild.md#logs).
 
-In Visual Studio, you can change the verbosity in **Tools** > **Options**, **Projects and Solutions**, **Build and Run**. See [How to: View, save, and configure build log files](../../ide/how-to-view-save-and-configure-build-log-files.md#to-change-the-amount-of-information-included-in-the-build-log).
+In Visual Studio, you can change the verbosity in **Tools** > **Options**, **Projects and Solutions**, **Build and Run**. See [How to: View, save, and configure build log files](../../ide/how-to-view-save-and-configure-build-log-files.md#specify-data-verbosity-for-build-logs).