Try to fix sphinx errors

Author: felicitymay

docs/codeql/codeql-for-visual-studio-code/using-the-codeql-model-editor.rst

@@ -13,6 +13,10 @@ TODO - EDIT THIS CONTENT!
 
 Explain how to find the data extension files that you've created and test them. Also how to save to the right location in a GitHub repository for default and advanced setup to use.
 
+Copy file into GitHub folder
+
+For testing:     "codeQL.runningQueries.useModelPacks": true, - does it work for MRVA
+
 About the CodeQL model editor
 -----------------------------
 
@@ -23,26 +27,6 @@ The editor takes a CodeQL database and runs some telemetry queries to identify u
 - Application mode: the editor identifies the external APIs used by the codebase. An external (or third party) API is any API that is not part of the CodeQL database you are analyzing. This mode is most useful for improving CodeQL results for the specific codebase.
 - Framework mode: the editor identifies the publicly accessible APIs in the codebase. This mode is most useful for improving the CodeQL results for any codebases that use those APIs.
 
-Setting up the CodeQL model editor
-----------------------------------
-
-To set up the CodeQL model editor, you need to be using CodeQL for VS Code 1.8.12 or later with the following settings: 
-
-.. code-block:: json
-
-{
-    "codeQL.canary": true,
-    "codeQL.model.editor": true,
-    "codeQL.runningQueries.useModelPacks": true,
-}
-
-CHECK THIS ^^^ - is canary still needed?
-
-Open the user settings editor (JSON) using the command palette (Ctrl/Cmd+Shift+P) and using the command “Preferences: Open User Settings (JSON)”, add these two settings to the file.
-
-If you want to test the CodeQL model packs you generate in VS Code then this setting is also required:
-   ``"codeQL.runningQueries.useExtensionPacks": true`` CHECK THIS - should it be ``"codeQL.runningQueries.useModelPacks": true``
-
 Using the CodeQL model editor
 -----------------------------
 
@@ -55,13 +39,16 @@ The easiest way to explain this is by using an example, so we'll run through an
 #. When the queries are complete, the APIs that have been identified are shown in the editor:
    - By default the editor runs in application mode, so displays the external APIs used by the codebase. 
    - If you switch to framework mode, the editor will display the publicly accessible APIs in the codebase.
+
 #. You can now start modeling the external API calls manually by selecting a model type and entering the correct values in each field, as defined in the Java models-as-data documentation
 #. You can generate the CodeQL automatically:
    - If you are working in application mode click on “Model from source” and enter the name of the repo that contains the source code for the package you want to model. For example, in this case you can enter dsp-testing/sql2o-import to download the relevant CodeQL database and model any APIs from that repo
    - If you are working in framework mode click on “Generate” to generate any models directly from the source code of the framework you are modeling.
+
 #. Once any modeling is complete, click “Save” or  “Save all”. You can now see that the calls are shown as supported. The generated models files are saved in your workspace at .github/codeql/extensions/<pack-name>, where the pack name is the same as the repo.
    - If you are in application mode, the editor will create a separate model file for each package that you model.
    - If you are in framework mode, the edit will generate a single model file for the entire framework.
+
 #. If you have set up VS Code to use data extensions (using the “codeQL.runningQueries.useExtensionPacks” setting), then you can also run a query and see that the unsafe calls are now detected.
 
 Known limitations