fix all markdownlint issues

docs/documentation/documentation.md

@@ -65,14 +65,17 @@ But you will find that most of it just works - and that once you get into a regu
 
 
 ### Step 1:  Pre-Requisites
+
 Assure you have been granted write access to our git repository.
-Make sure you have an account on GitHub and then contact dan@sartography.com and ask him to add you as a contributor.
+Make sure you have an account on GitHub and then contact `dan@sartography.com` and ask him to add you as a contributor.
 
 
 ### Step 2:  Install VSCode
+
 [Download VSCode](https://code.visualstudio.com/) and install it on your computer.
 
 ### Step 3: Install Python 
+
 We need python in order to build the website locally so we can really see what our content is going to look like once we publish.
 It's going to be handy for other reasons as well.
 We'll want python to be properly set up inside of VS Code.
@@ -80,11 +83,12 @@ Follow [these directions and brief tutorial](https://code.visualstudio.com/docs/
 
 
 ### Step 3: Connect VSCode to Git
+
 VSCode comes with Git built in.
 So you can use VSCode to "pull" changes from others down to your local computer and "push" changes back up to share with others (and to cause our docs site to rebuild).
 
 Here are directions for how to [clone Spiff-Arena](https://learn.microsoft.com/en-us/azure/developer/javascript/how-to/with-visual-studio-code/clone-github-repository?tabs=create-repo-command-palette%2Cinitialize-repo-activity-bar%2Ccreate-branch-command-palette%2Ccommit-changes-command-palette%2Cpush-command-palette#clone-repository).
-**IMPORTANT**: Follow those directions, but be sure to checkout https://github.com/sartography/spiff-arena instead of the project they are using!
+**IMPORTANT**: Follow those directions, but be sure to checkout `https://github.com/sartography/spiff-arena` instead of the project they are using!
 
 You can save the project to any directory on your computer.
 We strongly suggest you create a sub-folder called "projects" in your "home" or "Desktop" folder and checkout the code into this directory.  
@@ -103,6 +107,7 @@ Now click on the two pieces of paper at the top corner of your screen, and you s
 
 
 ### Step 4: Add some extensions
+
 * Inside VSCode, go to File -> Preferences -> Extensions
 * Search for "myst"
 * click the "install" button.
@@ -112,6 +117,7 @@ Now click on the two pieces of paper at the top corner of your screen, and you s
 
 
 ### Step 5: Install Python Dependencies
+
 This project requires a few Python dependencies to work correctly.
 We are going to set up a Virtual Environment for Python to keep us sane later on.
 You can do that by following these steps:
@@ -123,15 +129,18 @@ You can do that by following these steps:
 1. Click OK.
 
 ### Step 6: Fire up the website
+
 1. Go to Terminal ->  New Terminal
 1. type:  **sphinx-autobuild . _build/html** at the prompt and hit enter.
-1. Open your browser and go to http://127.0.0.1:8000
+1. Open your browser and go to [http://127.0.0.1:8000](http://127.0.0.1:8000).
 
 
 ### Step 7:  Make a change
+
 1. Open up a markdown file, and make a change. 
 
-### Step 8:  Commit your changes and push them up for everyone.
+### Step 8:  Commit your changes and push them up for everyone
+
 1. Select the "git" button on the left hand side of the toolbar (circles with lines between them) ![Git button](./images/git.png "Git button") 
 
 2. Press the blue "Commit" button.
@@ -140,8 +149,12 @@ You can do that by following these steps:
 
 ## Linting
 
+```{admonition} Linting is just an idea
+:class: warning
+
 Documentation people: please ignore this for now.
+```
 
 We may decide to check the documentation with a "linter" which is designed to keep the documentation consistent and standardized.
-One option is https://github.com/igorshubovych/markdownlint-cli, which uses https://github.com/DavidAnson/markdownlint, which seems to be more popular than https://github.com/markdownlint/markdownlint.
+One option is [markdownlint-cli](https://github.com/igorshubovych/markdownlint-cli), which uses David Anson's [NodeJS-based markdownlint](https://github.com/DavidAnson/markdownlint), which these days seems to be more popular than the [ruby-based markdownlint](https://github.com/markdownlint/markdownlint).
 A `.markdownlint.jsonc` file has been added that configures the same markdownlint program (basically to ignore the rule about long lines, since we are using ventilated prose).

docs/quick_start/quick_start.md

@@ -17,6 +17,7 @@ To access SpiffWorkflow, simply sign in using your Keycloak account. Once you ha
 :alt: Login Page
 :width: 45%
 ```
+
 ```{image} images/Untitled_1.png
 :alt: Home Page
 :width: 45%
@@ -60,6 +61,7 @@ The process section provides a comprehensive view of the process ecosystem by sh
 :class: info
 💡 A **process group** is a way of grouping a bunch of **process models.** A **process model** contains all the files necessary to execute a specific process.
 ```
+
 -- 
 ![Untitled](images/Untitled_4.png)
 
@@ -142,7 +144,7 @@ After starting a process, it's important to stay informed about its progress. Ev
 
 Here's how you can view the steps of the process you just started.
 
-### Step 1: Navigate to the “Home” or “Process Instance” section.
+### Step 1: Navigate to the “Home” or “Process Instance” section
 
 There are 2 ways of finding your process instances.
 
@@ -170,7 +172,7 @@ The Process-defined **metadata can provide valuable insights into its history, c
 
 To check the metadata of a process instance, follow these steps.
 
-### Step 1: Navigate to the “Home” or “Process Instance” section.
+### Step 1: Navigate to the “Home” or “Process Instance” section as before
 
 Once you're signed in, navigate to the home section. Here you will find a list of all the process instances you've initiated under **“Started by me”**.
 
@@ -231,7 +233,7 @@ To filter the list, click on the "Filter" option. This will expand the filter se
 
 ![Untitled](images/Untitled_20.png)
 
-### Step 3: Apply Filters:
+### Step 3: Apply Filters
 
 Once you have entered all the relevant filter details, click on the "**Apply**" button to apply the filters. The system will then display all the process instances matching the input details.