Fix urls

Author: hoijnet

src/app/blog/2022-02-14-json-diff-and-patch/page.md

@@ -26,7 +26,7 @@ Is it possible to do the same for structured data?
 
 These questions are really at the heart of the distributed part of web3. Web3 has other parts: immutability, cryptographic security, etc. But these other elements do not answer how to perform updates on distributed data stores.*
 
-In seeking the answer to these questions I was led to see a rather simple tool as foundational: [JSON diff and patch](https://terminusdb.com/products/jsondiff/).
+In seeking the answer to these questions I was led to see a rather simple tool as foundational: [JSON diff and patch](https://terminusdb.org/docs/json-diff-and-patch/).
 
 JSON, because JSON is the structured data format for the web. This will continue to be true for Web3. Everyone uses JSON for just about everything in our web architecture. Other formats are going to be increasingly used as mere optimizations of JSON. Associative arrays have the beauty of (reasonable) human readability, combined with widespread native support in modern computer programming languages. Both computers and humans can read it, what’s not to love!
 

src/app/blog/2022-02-14-many-worlds/page.md

@@ -336,7 +336,7 @@ collaboration puzzle?
 
 The first is the concept of structured patches. This issue is very
  close to my heart as it is what we are currently working on at
- [TerminusDB](https://terminusdb.com), and I've written some
+ [TerminusDB](https://terminusdb.org), and I've written some
  preliminary thoughts about it in a discussion on [patches](https://github.com/terminusdb/terminusdb/discussions/686).
 
 "There is nothing new under the sun" applies here. There are several

src/app/blog/2022-02-14-mongo-neo4j-terminusx/page.md

@@ -67,7 +67,7 @@ reference and a way to ensure that we have referential integrity
 storage data structures such that we can follow these links
 efficiently.
 
-In [TerminusDB](https://terminusdb.com/), we do this using URLs. This borrows from the original
+In [TerminusDB](https://terminusdb.org/), we do this using URLs. This borrows from the original
 concept of the HTML page, which is itself a structured document with
 hyper-links, but one designed for rendering rather than data
 manipulation.
@@ -86,9 +86,9 @@ look something like:
 
 We write down the references relative to the base URL prefix which we
 assume for our collection, which might be something like
-`http://terminusdb.com/db/Terminators/Humans/`. The fully-qualified
+`http://terminusdb.org/db/Terminators/Humans/`. The fully-qualified
 URL would be rendered as something like:
-`http://terminusdb.com/db/Terminators/Humans/Person/Jim+Smith`. This
+`http://terminusdb.org/db/Terminators/Humans/Person/Jim+Smith`. This
 makes it easier to read and write. But how do we know this is a
 reference and not a string? This is an important distinction for
 several reasons. It tells us how to index our objects such that
@@ -141,7 +141,7 @@ Web3 existed as a concept.
 
 Unfortunately it never really took off. There are many reasons for
 this, some of which are explored in [Graph Fundamentals Part 4: Linked
-Data](https://terminusdb.com/blog/graph-fundamentals-part-4-linked-data/).
+Data](https://terminusdb.org/blog/graph-fundamentals-part-4-linked-data/).
 
 Part of the reason for this is that RDF is somewhat hard to read, but
 even harder to write. Data is *completely* represented in the

src/app/blog/2022-02-14-syntactic-versioning/page.md

@@ -95,7 +95,7 @@ be found, communicated, and applied
 
 And if we were storing information as ASTs, rather than lines of text,
 we could store them in a [graph
-database](http://terminusdb.com). Imagine the kinds of testing and
+database](http://terminusdb.org). Imagine the kinds of testing and
 linting which could now take place. You could have a full graph query
 language at your disposal to search for problems and perform analysis!
 

src/app/blog/2022-06-14-terminusdb-10.1.0-the-mule/page.md

@@ -204,12 +204,12 @@ suggestions.
 
 ## Documentation Links
 
-[Diff](https://terminusdb.com/docs/index/json-diff-and-patch)
+[Diff](https://terminusdb.org/docs/index/json-diff-and-patch)
 
-[Capture IDs](https://terminusdb.com/docs/index/terminusx-db/reference-guides/document-interface?swcfpc=1#capturing-ids-while-inserting-or-replacing-documents)
+[Capture IDs](https://terminusdb.org/docs/index/terminusx-db/reference-guides/document-interface?swcfpc=1#capturing-ids-while-inserting-or-replacing-documents)
 
-[Type Inference](https://terminusdb.com/docs/index/terminusx-db/reference-guides/schema?swcfpc=1#inference)
+[Type Inference](https://terminusdb.org/docs/index/terminusx-db/reference-guides/schema?swcfpc=1#inference)
 
-[Unconstrained JSON](https://terminusdb.com/docs/index/terminusx-db/reference-guides/schema?swcfpc=1#json-type)
+[Unconstrained JSON](https://terminusdb.org/docs/index/terminusx-db/reference-guides/schema?swcfpc=1#json-type)
 
-[Document UI](https://terminusdb.com/docs/index/terminusx-db/how-to-guides/generate-document-user-interfaces/get-started-with-the-documents-user-interface)
+[Document UI](https://terminusdb.org/docs/index/terminusx-db/how-to-guides/generate-document-user-interfaces/get-started-with-the-documents-user-interface)

src/app/blog/2022-06-24-blank-nodes-in-rdf/page.md

@@ -53,7 +53,7 @@ Everything You Always Wanted to Know About Blank Nodes
 https://aidanhogan.com/docs/blank_nodes_jws.pdf
 ```
 
-[TerminusDB](https://terminusdb.com) makes this a lot easier with the latest release and provides capabilities to automatically derive subject/entity IDs based on either UUIDs, human-readable auto-incrementing values, or a content-aware hash.
+[TerminusDB](https://terminusdb.org) makes this a lot easier with the latest release and provides capabilities to automatically derive subject/entity IDs based on either UUIDs, human-readable auto-incrementing values, or a content-aware hash.
 
 Which is really really nice and straightforward.
 

src/app/docs/access-control-with-javascript/page.md

@@ -23,7 +23,7 @@ For credentials, you can use a JWT token, an API token or basic authentication w
 
 ```javascript
 //connect with the API token
-//(to request a token create an account in  https://terminusdb.com/)
+//(to request a token create an account in  https://terminusdb.org/)
 const accessContol = new AccessControl("https://servername.com",
 {organization:"my_team_name",
 token:"dGVybWludXNkYjovLy9kYXRhL2tleXNfYXB........"})
@@ -115,7 +115,7 @@ The API token to use to connect with DFRNT TerminusDB cloud
 
 ##### accessControl.setApiKey(atokenpi)
 
-Sets the API token for the object, to request a token create an account in https://terminusdb.com/
+Sets the API token for the object, to request a token create an account in https://terminusdb.org/
 
 Param