Fix some warnings in documentation

For eng/ide/ada_language_server#1705

Author: AnthonyLeonardoGracio

README.md

@@ -46,29 +46,6 @@ extension at
   - [Supported LSP Server Requests](#supported-lsp-server-requests)
     - [Protocol Extensions](#protocol-extensions)
   - [VS Code Extension](#vs-code-extension)
-    - [Getting Started](#getting-started)
-    - [Configuration](#configuration)
-    - [Refactoring](#refactoring)
-    - [Tasks](#tasks)
-      - [Task Customization](#task-customization)
-      - [Tasks for Project Mains](#tasks-for-project-mains)
-    - [Status Bar](#status-bar)
-    - [Alire Support](#alire-support)
-    - [GNATtest Support](#gnattest-support)
-      - [Using multi-root workspaces for test development](#using-multi-root-workspaces-for-test-development)
-      - [Limitations](#limitations)
-    - [GNATcoverage Support](#gnatcoverage-support)
-    - [Cross and Embedded Support](#cross-and-embedded-support)
-      - [GNATemulator Support](#gnatemulator-support)
-      - [Remote Debugging](#remote-debugging)
-    - [Working with Multiple Projects in the Same VS Code Workspace](#working-with-multiple-projects-in-the-same-vs-code-workspace)
-    - [Commands and Shortcuts](#commands-and-shortcuts)
-      - [Ada: Go to other file](#ada-go-to-other-file)
-      - [Ada: Add subprogram box](#ada-add-subprogram-box)
-      - [Ada: Reload project](#ada-reload-project)
-      - [Tasks with keyboard shortcuts](#tasks-with-keyboard-shortcuts)
-    - [Bug Reporting](#bug-reporting)
-    - [Limitations and Differences with GNAT Studio](#limitations-and-differences-with-gnat-studio)
   - [Integration with other editors and IDEs](#integration-with-other-editors-and-ides)
     - [Integration with Coc.NVim](#integration-with-cocnvim)
     - [Integration with vim-lsp](#integration-with-vim-lsp)

doc/Set-workspace-specific-environment-variables.md

@@ -3,7 +3,7 @@
 
 This small tutorial will help you to create a workspace-specific environment, allowing you to set and/or modify environment variables for your project (e.g: put the needed toolchain in front of your `PATH`).
 
-This is particularly useful when working on [remote machines](Working-on-a-remote-machine) in order 
+This is particularly useful when working on [remote machines](Working-on-a-remote-machine) in order
 to avoid modifying the environment globally just to work on a given project.
 
 ## Prerequisites
@@ -23,33 +23,33 @@ Extensions view (`Ctrl+Shift+X`).
 
 Basically you just need to specify your environment variables and their associated values via the `terminal.integrated.env.*` VS Code settings in your workspace file (or your `settings.json` file), like in the following example:
 
-```
-	// Set a workspace-specific environment for OSX platforms.
-	"terminal.integrated.env.osx": {
-	        //  Set MAIN_NUMBER scenario variable to MAIN_2 directly from the environment
-		"MAIN_NUMBER": "MAIN_2",
+```json
+ // Set a workspace-specific environment for OSX platforms.
+ "terminal.integrated.env.osx": {
+         //  Set MAIN_NUMBER scenario variable to MAIN_2 directly from the environment
+  "MAIN_NUMBER": "MAIN_2",
 
                 //  Set custom GPR_PROJECT_PATH
-		"GPR_PROJECT_PATH": "${workspaceFolder}/imported:${env:GPR_PROJECT_PATH}:"
+  "GPR_PROJECT_PATH": "${workspaceFolder}/imported:${env:GPR_PROJECT_PATH}:"
         },
 
-	// Set a workspace-specific environment for Linux platforms.
-	"terminal.integrated.env.linux": {
-	        //  Set MAIN_NUMBER scenario variable to MAIN_2 directly from the environment
-		"MAIN_NUMBER": "MAIN_2",
+ // Set a workspace-specific environment for Linux platforms.
+ "terminal.integrated.env.linux": {
+         //  Set MAIN_NUMBER scenario variable to MAIN_2 directly from the environment
+  "MAIN_NUMBER": "MAIN_2",
 
                 //  Set custom GPR_PROJECT_PATH
-		"GPR_PROJECT_PATH": "${workspaceFolder}/imported:${env:GPR_PROJECT_PATH}:"
+  "GPR_PROJECT_PATH": "${workspaceFolder}/imported:${env:GPR_PROJECT_PATH}:"
         },
 
-	// Set a workspace-specific environment for Windows
-	"terminal.integrated.env.windows": {
-		//  Set MAIN_NUMBER scenario variable to MAIN_2 directly from the environment
-		"MAIN_NUMBER": "MAIN_2",
+ // Set a workspace-specific environment for Windows
+ "terminal.integrated.env.windows": {
+  //  Set MAIN_NUMBER scenario variable to MAIN_2 directly from the environment
+  "MAIN_NUMBER": "MAIN_2",
 
                 //  Set custom GPR_PROJECT_PATH
-		"GPR_PROJECT_PATH": "${workspaceFolder}\\imported;${env:GPR_PROJECT_PATH}:"
-	}
+  "GPR_PROJECT_PATH": "${workspaceFolder}\\imported;${env:GPR_PROJECT_PATH}:"
+ }
 ```
 
 ## Example

doc/settings.md

@@ -106,7 +106,7 @@ Settings understood by the Ada Language Server itself, independently from the LS
 * [defaultCharset](#defaultcharset)
 * [relocateBuildTree](#relocatebuildtree)
 * [rootDir](#rootdir)
-* [enableDiagnostics](#enableddiagnostics)
+* [enableDiagnostics](#enablediagnostics)
 * [adaFileDiagnostics](#adafilediagnostics)
 * [gprFileDiagnostics](#gprfilediagnostics)
 * [sourceInfoDiagnostics](#sourceinfodiagnostics)

doc/tips_and_tricks.rst

@@ -9,4 +9,4 @@ Tips and tricks
    Custom-colors-in-VS-Code
    Project-file-editing
    Set-workspace-specific-environment-variables
-   Working-on-a-remote-machine.md
+   Working-on-a-remote-machine.md