Updated links

trustoverip · Jan 27, 2025 · 291e8ba · 291e8ba
1 parent 997b8ae
commit 291e8ba
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/docs/advanced-features/add.md b/docs/advanced-features/add.md
@@ -28,7 +28,7 @@ git init
 cd ..
 ```
 
-Now that you're outside the repo directory (!): Go over [Installation](../getting-started/installation) and create a new repo with the established name. In the example `Main-KERI-glossary`, you start with: 
+Now that you're outside the repo directory (!): Go over [Installation](../getting-started/installation/installation) and create a new repo with the established name. In the example `Main-KERI-glossary`, you start with: 
 
 ```
 npx create-spec-up-t < established dirname >

diff --git a/docs/faq.md b/docs/faq.md
@@ -36,7 +36,7 @@ Unlike the DIF Spec-Up repository, the Spec-Up-T repository **does not generate
 
 This functionality has been moved to the Spec-Up-T *installer*. Spec-Up-T is now an NPM package that should be installed via `package.json`.
 
-For more details, refer to [the installation section](./getting-started/installation.md).
+For more details, refer to [the installation section](./getting-started/installation/installation.md).
 
 :::
 

diff --git a/docs/introduction/target-audience.md b/docs/introduction/target-audience.md
@@ -22,6 +22,6 @@ Spec-Up-<span className="rotate">T</span> is based on **Spec-Up**, and some of t
 
 :::tip
 
-If you aren't contributing to an existing Spec-Up-T project and want to create one yourself, you will have to install Spec-Up-T to start using it. Go straight to the [installation section](../getting-started/installation.md) for instructions. If you are contributing to an existing Spec-Up-T project you can contribute to content directly within GitHub's web editor (for example) by editing and adding the appropriate markdown files.
+If you aren't contributing to an existing Spec-Up-T project and want to create one yourself, you will have to install Spec-Up-T to start using it. Go straight to the [installation section](../getting-started/installation/installation.md) for instructions. If you are contributing to an existing Spec-Up-T project you can contribute to content directly within GitHub's web editor (for example) by editing and adding the appropriate markdown files.
 
 :::
diff --git a/docs/user-interface-overview/command-line-menu.md b/docs/user-interface-overview/command-line-menu.md
@@ -16,7 +16,7 @@ Still, it can be confusing. And if you're used to a regular application you cont
 Currently, the menu is only tested on MacOs and has not been tested on Windows OS.
 :::
 
-Assuming you already [installed](../getting-started/installation.md) Spec-Up-T, here you find further instructions.
+Assuming you already [installed](../getting-started/installation/installation.md) Spec-Up-T, here you find further instructions.
 
 To start, run this command in the terminal:
-Original file line number
+Diff line change
@@ Expand Up / @@ -28,7 +28,7 @@ git init @@
     cd ..
     ```
-    Now that you're outside the repo directory (!): Go over [Installation](../getting-started/installation) and create a new repo with the established name. In the example `Main-KERI-glossary`, you start with:
+    Now that you're outside the repo directory (!): Go over [Installation](../getting-started/installation/installation) and create a new repo with the established name. In the example `Main-KERI-glossary`, you start with:
     ```
     npx create-spec-up-t < established dirname >
@@ Expand Down @@