fix broken links

OpenFn · Feb 10, 2024 · 1e6a113 · 1e6a113
1 parent 53db655
commit 1e6a113
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 5 deletions.
diff --git a/docs/get-started/glossary.md b/docs/get-started/glossary.md
@@ -13,7 +13,7 @@ further reading if you want a better understanding of some part of your data
 integration picture.
 
 Note: This glossary is meant to be OpenFn-agnostic. The rest of the docs and
-[Key Concepts page](/documentation/get-started/terminology) help you to get a
+[Key Concepts page](/documentation/next/get-started/terminology) help you to get a
 picture of the parts of OpenFn, what we call them, and why, but this glossary is
 really meant as a prerequisite to all those other things to aid users with no
 experience in this area.

diff --git a/docs/get-started/home.md b/docs/get-started/home.md
@@ -108,7 +108,7 @@ OpenFn v2 (see above).
 
 ### OpenFn developer tooling
 
-[OpenFn/kit](/documentation/kit) provides a CLI and set of developer tools for
+[OpenFn/kit](https://github.com/OpenFn/kit) provides a CLI and set of developer tools for
 writing & testing workflows, managing OpenFn projects, and developing
 [Adaptors](https://github.com/openfn/adaptors).
 

diff --git a/docs/get-started/terminology.md b/docs/get-started/terminology.md
@@ -19,7 +19,7 @@ or ask on the [Community](https://community.openfn.org)
 
 Please note that if you're looking for a glossary for generic terms used in
 data-integration (rather than this _OpenFn-specific_ stuff) head over to the
-[Glossary for Integration](/documentation/get-started/glossary) page in the
+[Glossary for Integration](/documentation/next/get-started/glossary) page in the
 Design section. Otherwise, read on!
 
 ## Project
@@ -103,7 +103,7 @@ Credentials are the **"how to log in"** part of automation!
 
 :::
 
-A [Credential](/documentation/next/manage-projects/manage-credentials) is used
+A Credential is used
 to authenticate with a destination app (e.g., Database username, password &
 login URL) so that a Workflow Step can run. Via OpenFn's security model,
 Credentials are separated from the Workflows themselves to ensure that stored
@@ -121,7 +121,7 @@ Triggers are the **"when to do it"** part of automation!
 A [Trigger](/documentation/build/triggers) determines **how and when** Workflows
 should execute automatically (e.g., real-time or schedule-based). When
 activated, Triggers create a new
-[Work Order](/documentation/get-started/terminology#work-order) and run (or
+[Work Order](/documentation/next/get-started/terminology#work-order) and run (or
 "execute") the Workflow.
 
 A "Webhook Event" Trigger may be configured if you want your Workflow to execute