Fix broken doc links

Author: PEZ

docs/site/connect.md

@@ -131,4 +131,4 @@ If you've added environment variables in your OS, such as in your `~/.bashrc` fi
 
 ### Viewing the Communication Between nREPL and Calva
 
-It may be helpful to view the messages sent between nREPL and Calva when troubleshooting an issue related to the REPL. See how to do that [here](../nrepl_and_cider-nrepl/#viewing-the-communication-between-calva-and-nrepl).
+It may be helpful to view the messages sent between nREPL and Calva when troubleshooting an issue related to the REPL. See how to do that [here](nrepl_and_cider-nrepl.md#viewing-the-communication-between-calva-and-nrepl).

docs/site/customizing-jack-in-and-connect.md

@@ -157,7 +157,7 @@ When searching for project roots in your workspace, Calva will glob for all file
 
 ### Viewing the Communication Between nREPL and Calva
 
-It may be helpful to view the messages sent between nREPL and Calva when troubleshooting an issue related to the REPL. See how to do that [here](../nrepl_and_cider-nrepl/#viewing-the-communication-between-calva-and-nrepl).
+It may be helpful to view the messages sent between nREPL and Calva when troubleshooting an issue related to the REPL. See how to do that [here](nrepl_and_cider-nrepl.md#viewing-the-communication-between-calva-and-nrepl).
 
 ## Etcetera
 

docs/site/formatting.md

@@ -72,7 +72,7 @@ Unlike with the ”real” Calva Formatter, which never breaks up lines, this on
 
 #### Provide zprint config via keyboard shortcuts (or Joyride)
 
-The default options for the command are to not sort maps and to not insert commas between map entries. However, the command takes a map as an argument, expecting this map to be a [zprint configuration]((https://github.com/kkinnear/zprint/blob/main/doc/reference.md)) map. You can provide the argument map via keyboard shortcuts. In VS Code settings, you use JSON, but it will be converted to EDN before handed to zprint.
+The default options for the command are to not sort maps and to not insert commas between map entries. However, the command takes a map as an argument, expecting this map to be a [zprint configuration](https://github.com/kkinnear/zprint/blob/main/doc/reference.md) map. You can provide the argument map via keyboard shortcuts. In VS Code settings, you use JSON, but it will be converted to EDN before handed to zprint.
 
 Say you want to have maps sorted by their keys, and generally use community standard formating + justify maps and bindings. This keyboard shortcut does that.
 

docs/site/get-started-with-clojure.md

@@ -72,7 +72,7 @@ The instructions will be in the form of Clojure comments, and you will be runnin
 
 The command to run is: **Calva: Create a Getting Started REPL project**.
 
-![VS Code Command Palette, Calva Getting Started](/images/getting-started-with-clojure/vscode-command-palette-calva-getting-started.png)
+![VS Code Command Palette, Calva Getting Started](images/getting-started-with-clojure/vscode-command-palette-calva-getting-started.png)
 
 That's it. Do it now. This page has some more information to make the start of your Clojure adventure fun and smooth. It ain't going anywhere, though. 😀 Come back to it.
 

docs/site/getting-started.md

@@ -35,7 +35,7 @@ The demo tells you about the command (and some about the Clojure Beginner's mate
 
 If you are new to Calva, a good place to start is using the command **Calva: Create a ”Getting Started” REPL**. (You can open the command palette using the VS Code top menu by going to `View -> Command Palette...` or by running the associated keyboard shortcut for your OS.) Demo:
 
-![Command Palette Getting Started REPL](/images/getting-started-with-clojure/vscode-command-palette-calva-getting-started.png "Create a ”Getting Started” REPL")
+![Command Palette Getting Started REPL](images/getting-started-with-clojure/vscode-command-palette-calva-getting-started.png "Create a ”Getting Started” REPL")
 
 See the [Getting Started with Clojure](get-started-with-clojure.md) guide for a bit more about this feature.
 

docs/site/merch.md

@@ -43,7 +43,7 @@ There are four design, all featuring the Calva symbol (the Calva glass), which a
 
 #### Symbol + Logo
 
-![Calva T-shirt Symbol + Logo](/images/merch/t-shirt-calva-symbol-and-logo.png)
+![Calva T-shirt Symbol + Logo](images/merch/t-shirt-calva-symbol-and-logo.png)
 
 Available at:
 
@@ -61,7 +61,7 @@ Available at:
 
 The Calva symbol and Logo front, Rich Comments back.
 
-![Calva T-shirt We do it with Rich Comments Back](/images/merch/calva-t-shirt-symbol+logo+rich-comments.png)
+![Calva T-shirt We do it with Rich Comments Back](images/merch/calva-t-shirt-symbol+logo+rich-comments.png)
 
 Available at:
 
@@ -77,7 +77,7 @@ Available at:
 
 #### Symbol Only
 
-![Calva T-shirt Symbol](/images/merch/t-shirt-calva-symbol.png)
+![Calva T-shirt Symbol](images/merch/t-shirt-calva-symbol.png)
 
 Available at:
 
@@ -95,7 +95,7 @@ Available at:
 
 The Calva symbol front, Rich Comments Back.
 
-![Calva T-shirt We do it with Rich Comments Back](/images/merch/calva-t-shirt-symbol+rich-comments.png)
+![Calva T-shirt We do it with Rich Comments Back](images/merch/calva-t-shirt-symbol+rich-comments.png)
 
 Available at:
 

docs/site/shadow-cljs.md

@@ -55,7 +55,7 @@ Use the command **Calva: Select Shadow CLJS Runtime** to see all runtimes that a
 
 The **Calva: Select Shadow CLJS Runtime** menu will also let you select which runtime the `cljs` repl is connected to.
 
-![shadow-cljs-runtimes-menu](/images/shadow-cljs/runtimes-menu.png)
+![shadow-cljs-runtimes-menu](images/shadow-cljs/runtimes-menu.png)
 
 ## Automatic tracking of current runtime
 

docs/site/why-calva.md

@@ -13,7 +13,7 @@ We who make Calva are actively [stewarding, maintaining, documenting and support
 
 Calva has very happy users! Check out the Programming Languages section on the Visual Studio Code Marketplace, [sorted by rating](https://marketplace.visualstudio.com/search?target=VSCode&category=Programming%20Languages&sortBy=Rating):
 
-![VS Code Extensions by Rating](/images/vscode-extension-by-rating.png)
+![VS Code Extensions by Rating](images/vscode-extension-by-rating.png)
 
 Recently there was a [thread over at ClojureVerse](https://clojureverse.org/t/gnu-emacs-cider-vs-vs-code-calva/7829/26), asking about how Calva Compares to Emacs with [CIDER](https://cider.mx). It is well worth reading. We would like to highlight [the answer by Nick Cernis](https://clojureverse.org/t/gnu-emacs-cider-vs-vs-code-calva/7829/26), which focuses on Calva. We'll even quote parts of it. 😍
 
@@ -30,14 +30,14 @@ Recently there was a [thread over at ClojureVerse](https://clojureverse.org/t/gn
 >
 > …
 >
-> I started with the jaded assumption that VS Code was probably bad because it's built by committee at Microsoft on a web-tech based Electron stack, only to find that it succeeds in embodying the spirit of a “hacker's editor” more than even Emacs does in many ways: 
+> I started with the jaded assumption that VS Code was probably bad because it's built by committee at Microsoft on a web-tech based Electron stack, only to find that it succeeds in embodying the spirit of a “hacker's editor” more than even Emacs does in many ways:
 >
 > …
 >
 > **On the benefits of Calva:**
-> 
+>
 > - **Of all the amazing Clojure community projects, Calva seems most likely to encourage new users to try Clojure and ClojureScript**. A lot of developers use VS Code. It’s been tricky to convince frontend developer friends to try ClojureScript, but at least they don’t have the excuse that they’ll need to switch editors to even try it now. I think as a community we should try to support the projects that encourage Clojure’s adoption and ease of use, including by using those products ourselves.
-> 
+>
 > - **Calva provides a better first-time experience than any other editor/plugin combo whether you’re new to Clojure or not.** You can install the plugin and be chatting with your REPL in under a minute without any knowledge of Elisp or VimScript/Lua or how to configure Run Configurations in IntelliJ.
 > - **The default key bindings are good and the commands are easily discoverable.**
 > - **For its age it’s surprisingly feature rich.**
@@ -55,7 +55,7 @@ We are super proud of the [Calva reviews on the Visual Studio Code Marketplace](
 ---
 
 > ★️️️️️★️️️️️★️️️️️★️️️️️★️️️️️ **Calva hits the sweet spot of being both approachable for new users and powerful for seasoned ones.**
-> 
+>
 > The creators/maintainers are fantastic individuals that care deeply about streamlining the user experience, and it shows.
 >
 > Good stuff, check it out.
@@ -65,7 +65,7 @@ We are super proud of the [Calva reviews on the Visual Studio Code Marketplace](
 ---
 
 > ★️️️️️★️️️️️★️️️️️★️️️️️★️️️️️ **I switched from IntelliJ / Cursive to VS Code and Calva and it's been amazing.**
-> 
+>
 > ...
 >
 > That is the biggest thing I can say for Calva, it just works. I was never a fan of VS Code before, but VS Code + Calva for Clojure is now my favorite language / IDE experience.
@@ -83,7 +83,7 @@ We are super proud of the [Calva reviews on the Visual Studio Code Marketplace](
 > It already has great REPL support (including inline evaluation), an extensive Paredit implementation, and excellent linting (care of the bundled clj-kondo). Calva is being improved on at an impressive clip by maintainers who appear solidly committed to its ongoing development. It's well-documented, and manages to be both approachable and capable.
 >
 > A no-brainer if you're already a VS Code user, and well worth a look if you're not.
-> 
+>
 > _Crispin Bennett_
 
 ---
@@ -93,6 +93,6 @@ We are super proud of the [Calva reviews on the Visual Studio Code Marketplace](
 > I joined the Slack channel about 2 wks ago and I must say that I'm very impressed by how active and responsive this community is. Already 2 of my issues fixed and I really like Calva (and the extensions it uses!).
 >
 > These are professional people and they make me very happy!
-> 
+>
 > _Uitbeijerse, E (Eric)_