Updated docs per reviwer comments

Author: 1eyewonder

docs/content/getting-started/CLI.md

@@ -8,19 +8,13 @@ index: 3
 
 ## Example Command
 
-When running the CLI tool from the command line, the bare minimum you need to provide is the path to the project file(s) you want to analyze.
-
-```shell
-dotnet fsharp-analyzers --project ./YourProject.fsproj
-```
-
-An optional argument you may need to provide is `--analyzers-path`. This is the path to the directory containing the analyzer DLLs. 
+When running the CLI tool from the command line (and after installing analyzers), the minimum console arguments you need to provide is the path to the project file(s) you want to analyze.
 
 ```shell
 dotnet fsharp-analyzers --project ./YourProject.fsproj --analyzers-path ./path/to/analyzers/directory
 ```
 
-⚠️ If you don't provide this argument, it will default to `packages/analyzers`.
+⚠️ If you don't provide the `--analyzers-path` argument, it will default to `packages/analyzers`. If you are using Paket with a group called `analyzers`, this default path should work for you.
 
 ## Viewing Additional Commands
 

docs/content/getting-started/Configuring for IDE.md

@@ -8,16 +8,16 @@ index: 2
 
 ## Visual Studio Code
 
-In order to configure analyzers for VSCode, you will need to update your project's `.vscode/settings.json` file or your user settings. You should only need the following settings:
+In order to configure analyzers for VSCode, you will need to update your project's `.vscode/settings.json` file or your user settings. You should need the settings shown below.
 
 ```json
 {
   "FSharp.enableAnalyzers": true,
-  "FSharp.analyzersPath": ["packages/analyzers"]
+  "FSharp.analyzersPath": ["path/to/analyzers/directory"]
 }
 ```
 
-📓 Note: The path in `FSharp.analyzersPath` above is currently pointing to the path we set up in the Paket example on the [installation page]({{fsdocs-previous-page-link}}).
+📓 Note: Issue created [here](https://github.com/ionide/FsAutoComplete/issues/1350) regarding analyzers & SDK mismatches in the logs
 
 After saving your new settings, make sure to restart VSCode. Once VSCode restarts, you should be able to test and see if the analyzers are working by opening a F# file in your workspace and entering the following code
 

docs/content/getting-started/Installing Analyzers.md

@@ -10,7 +10,7 @@ index: 1
 A dotnet CLI tool, called [fsharp-analyzers](https://github.com/ionide/FSharp.Analyzers.SDK/), is used to run analyzers outside the context of an IDE. Add it to your tool-manifest with:
 
 ```shell
-dotnet tool install fsharp-analyzers
+dotnet tool install fsharp-analyzers --create-manifest-if-needed
 ```
 
 ## Installing Analyzers