Fix for correct linking

Author: hoijnet

src/app/docs/document-graph-api/page.md

@@ -33,4 +33,4 @@ The easiest way to get started with the document API is to use the TerminusDB cl
 * [Document Insertion Reference Guide](/docs/document-insertion/)
 * [Documents in a knowledge graph and how to use them](/docs/documents-explanation/)
 * [Immutability, version history, and revision control](/docs/immutability-explanation/)
-* [GraphQL API](/docs/how-to-query-with-graphql)
+* [GraphQL API](/docs/how-to-query-with-graphql/)

src/app/docs/document-insertion/page.md

@@ -497,7 +497,7 @@ The result of this POST request is either an updated branch with a successful ap
 
 ## Version control commit id feedback
 
-When a commit is made, the `TerminusDB-Data-Version` header is returned, which is the reference to the commit made in the [version history](/docs/immutability-explanation). This header can be used to retrieve the exact copy of the document from the specific version in the immutable history.
+When a commit is made, the `TerminusDB-Data-Version` header is returned, which is the reference to the commit made in the [version history](/docs/immutability-explanation/). This header can be used to retrieve the exact copy of the document from the specific version in the immutable history.
 
 To get the specific version, use the branchspec `org/dataproduct/local/commit/:commitId` where `:commitId` is the value of the right hand side of the colon separated value in the `TerminusDB-Data-Version` header.
 

src/app/docs/git-for-data-reference/page.md

@@ -13,7 +13,7 @@ media: []
 
 Git-for-Data is a feature of TerminusDB that allows you to use git-like operations on TerminusDB data product branches, including the ability to transport data between TerminusDB instances using `clone`, `push`, `pull` and `fetch`.
 
-This is useful to collaborate on information by syncronizing content repositories with [cloud-hosted TerminusDB instances](https://dfrnt.com/hypergraph-content-studio/), and also between environments where network segmentation is strict, such as in IEC62443, Purdue model and other environments, as described in [Transfer data in operational technologies landscapes](/docs/operational-technologies-transfer). 
+This is useful to collaborate on information by syncronizing content repositories with [cloud-hosted TerminusDB instances](https://dfrnt.com/hypergraph-content-studio/), and also between environments where network segmentation is strict, such as in IEC62443, Purdue model and other environments, as described in [Transfer data in operational technologies landscapes](/docs/operational-technologies-transfer/). 
 
 In addition to the transportation of data between TerminusDB instances, Git-for-Data also allows you to manage data product branches using equivalents to `rebase` (replay commits onto a separate branch) and `merge` (apply) commands.
 
@@ -85,8 +85,8 @@ The `reset` operation resets a branch to a previous commit, discarding all commi
 
 ### Diff and patch
 
-`diff` and `patch` operations are available to compare and apply specific changes between branches of data products. These operations are described in [JSON Diff and Patch](/docs/json-diff-and-patch).
+`diff` and `patch` operations are available to compare and apply specific changes between branches of data products. These operations are described in [JSON Diff and Patch](/docs/json-diff-and-patch/).
 
 ## More about git-for-data
 
-Read more about how git-for-data can be used in operational technologies environments in [Transfer data in operational technologies landscapes](/docs/operational-technologies-transfer), and how to clone individual branches of data products in [Manual Reverse Branch Cloning](/docs/manual-reverse-branch-cloning).
+Read more about how git-for-data can be used in operational technologies environments in [Transfer data in operational technologies landscapes](/docs/operational-technologies-transfer/), and how to clone individual branches of data products in [Manual Reverse Branch Cloning](/docs/manual-reverse-branch-cloning/).

src/app/docs/manual-reverse-branch-cloning/page.md

@@ -24,4 +24,4 @@ How to reverse clone a data product branch from a localhost instance to a cloud
 1. Move any additional branches that should be moved
 1. Copy title, description and other attributes of the data product to the cloud version. 
 
-Read more about [git-for-data](/docs/git-for-data-reference) for more information on how to use TerminusDB and git-for-data.
+Read more about [git-for-data](/docs/git-for-data-reference/) for more information on how to use TerminusDB and git-for-data.

src/app/docs/operational-technologies-transfer/page.md

@@ -19,4 +19,4 @@ TerminusDB is well positioned for data transports in such environments thanks to
 
 An analytics data product can be pushed in layers (between TerminusDB instances) all the way to a DMZ network handoff point, and then `pull`ed from the DMZ into the IT environment. This prevents any outbound communication from the DMZ environment, whilst the information can flow as part of a digital twin of the operational environment.
 
-Read more about the git-for-data of knowledge graphs in the [Git-for-Data Reference](/docs/git-for-data-reference) page.
+Read more about the git-for-data of knowledge graphs in the [Git-for-Data Reference](/docs/git-for-data-reference/) page.

src/app/docs/woql-getting-started/page.md

@@ -11,7 +11,7 @@ nextjs:
 media: []
 ---
 
-The thinking behind the Web Object Query Language is well explained on the [WOQL explanation](/docs/woql-explanation) page. As mentioned there, it is a formal language for querying and updating TerminusDB databases. As a language is builds on a declarative datalog foundation, and is evaluated by binding variables as the abstract syntax tree is read.
+The thinking behind the Web Object Query Language is well explained on the [WOQL explanation](/docs/woql-explanation/) page. As mentioned there, it is a formal language for querying and updating TerminusDB databases. As a language is builds on a declarative datalog foundation, and is evaluated by binding variables as the abstract syntax tree is read.
 
 This means that some logical behaviours depend on the order of binding the variables to values in the current instance or schema graph that is addressed.