Update faq.md

Author: dsyme

docs/faq.md

@@ -14,40 +14,44 @@
 
    If your failures only happen in the IDE then use `devenv /debugexe devenv.exe MyProj.fsproj`, set debug type to  ".NET Framework 4.0" and launch F5. Likewise if your failures only happen in F# Interactive then use `devenv /debugexe fsi.exe MyProj.fsproj`.
 
-   Set first-catch exception handling (Ctrl-Alt-E, select all CLR exceptions) and set Just My Code off
+Set first-catch exception handling (Ctrl-Alt-E, select all CLR exceptions) and set Just My Code off
 
 ## A dependency of my type provider is not loading, what do I do?
 
 For example, let's say you have this error in your test project:
 
-```
+```text
 2>E:\GitHub\admin\joe-provider\test\Joe.Test\ProviderTests.fs(8,10): error FS3033: The type provider 'Joe.Provider.JoeProvider' reported an error: Could not load file or assembly 'Newtonsoft.Json, Version=12.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'. The system cannot find the file specified. [E:\GitHub\dsyme\joe-provider\test\Joe.Test\Joe.Test.fsproj]
 ```
 
 Here your test project is referencing your provider project, and your type provider has a dependency on `Newtonsoft.Json.dll`. To see what's going on, run
 
-    dotnet build -v:n
-    
+```text
+dotnet build -v:n
+```
+
 In the compilation of your test project you will see something like this:
 
-         C:\Program Files\dotnet\dotnet.exe "C:\Program Files\dotnet\sdk\3.1.401\FSharp\fsc.exe"
-             -o:obj\Debug\net5.0\Joe.Test.dll
-             ...
-             -r:E:\GitHub\admin\joe-provider\src\Joe.Provider\bin\Debug\netstandard2.0\Joe.Provider.dll
-             ...
+```text
+    C:\Program Files\dotnet\dotnet.exe "C:\Program Files\dotnet\sdk\3.1.401\FSharp\fsc.exe"
+         -o:obj\Debug\net5.0\Joe.Test.dll
+         ...
+         -r:E:\GitHub\admin\joe-provider\src\Joe.Provider\bin\Debug\netstandard2.0\Joe.Provider.dll
+         ...
+```
 
 1. The tool `fsc.exe` is trying to load the type provider but a dependency is not found.  As mentioned above, all dependencies must be packaged
    alongside your design time component.  For example, adding
 
-       <Content Include="..\..\packages\Newtonsoft.Json\lib\netstandard2.0\Newtonsoft.Json.dll" CopyToOutputDirectory="PreserveNewest" />
+   ```text
+   <Content Include="..\..\packages\Newtonsoft.Json\lib\netstandard2.0\Newtonsoft.Json.dll" CopyToOutputDirectory="PreserveNewest" />
+   ```
 
    will include the component and unblock you.  However, you will need to be careful to make sure this component is laid down in the right place in your nuget
    package, see the instructions above for what the final layout of the nuget package should be.
 
 2. When making type providers whose design-time components have dependencies, you should always use a "split" type provider that separates the design-time and runtime components.
 
-TODO: give exact .fsproj/nuget instructions to get the dependency into the `typeproviders\fsharp41\netstandard2.0` directory alongside the design-time component.
-
 ## How do I debug execution of a type provider when using .NET Core tools on Windows?
 
 One approach:
@@ -56,11 +60,15 @@ One approach:
 
 2. Run an explicit invocation of the compiler using:
 
-       "c:\Program Files\dotnet\dotnet.exe" "C:\Program Files\dotnet\sdk\2.1.403\FSharp\fsc.exe" @args.txt
+   ```text
+   "c:\Program Files\dotnet\dotnet.exe" "C:\Program Files\dotnet\sdk\2.1.403\FSharp\fsc.exe" @args.txt
+   ```
 
    Then debug that invocation using
 
-       devenv /debugexe "c:\Program Files\dotnet\dotnet.exe" "C:\Program Files\dotnet\sdk\2.1.403\FSharp\fsc.exe" @args.txt
+   ```text
+   devenv /debugexe "c:\Program Files\dotnet\dotnet.exe" "C:\Program Files\dotnet\sdk\2.1.403\FSharp\fsc.exe" @args.txt
+   ```
 
    Be careful to make sure Visual Studio debugging type is set to ".NET Core" (right click properties on dotnet and set debug type)