diff --git a/docs/getting-started/connect-to-data/_databaseDocs/_clickHouse/_02-create-source-metadata.mdx b/docs/getting-started/connect-to-data/_databaseDocs/_clickHouse/_02-create-source-metadata.mdx
index b6d60542f..d25ba1ef0 100644
--- a/docs/getting-started/connect-to-data/_databaseDocs/_clickHouse/_02-create-source-metadata.mdx
+++ b/docs/getting-started/connect-to-data/_databaseDocs/_clickHouse/_02-create-source-metadata.mdx
@@ -1,10 +1,11 @@
-import BaseUrlLink from '@site/src/components/databaseDocs/baseLink';
+import BaseUrlLink from "@site/src/components/databaseDocs/baseLink";
 
 ## What's about to happen?
 
-After initializing a connector and creating a JSON configuration, which represents our tables in ClickHouse, we can use
-it to generate Hasura metadata. In the steps below, we'll utilize our `configuration.json` — populated by introspecting
-our ClickHouse database — to create metadata which Hasura can use to construct our API.
+After initializing a ClickHouse connector and creating a JSON configuration, which represents our tables in a format
+which the connector specifies, we can use it to generate Hasura metadata. In the steps below, we'll utilize our
+`configuration.json` — populated by introspecting our ClickHouse database — to create metadata which Hasura can use to
+construct our API.
 
 ## Step 1. Create the Hasura metadata
 
@@ -19,7 +20,7 @@ our ClickHouse database — to create metadata which Hasura can use to construct
 
 <!-- prettier-ignore -->
 Hasura DDN uses a concept called "connector linking" to take [NDC-compliant](https://github.com/hasura/ndc-spec)
-configuration JSON files for a data connector and transform them into an `hml` (Hasura Metadata Language) file as a <BaseUrlLink to="/supergraph-modeling/data-connectors/" text="DataConnectorLink" /> metadata object.
+configuration JSON files for a data connector and transform them into an `hml` (Hasura Metadata Language) file as a <BaseUrlLink to="/supergraph-modeling/data-connector-links/" text="DataConnectorLink" /> metadata object.
 
 Basically, metadata objects in `hml` files define our API.
 
@@ -57,7 +58,7 @@ schema:
     functions: []
     procedures: []
   capabilities:
-    version: ''
+    version: ""
     capabilities:
       query: {}
       mutation: {}
diff --git a/docs/getting-started/connect-to-data/_databaseDocs/_mongoDB/_02-create-source-metadata.mdx b/docs/getting-started/connect-to-data/_databaseDocs/_mongoDB/_02-create-source-metadata.mdx
index 3522d6827..338321a9e 100644
--- a/docs/getting-started/connect-to-data/_databaseDocs/_mongoDB/_02-create-source-metadata.mdx
+++ b/docs/getting-started/connect-to-data/_databaseDocs/_mongoDB/_02-create-source-metadata.mdx
@@ -1,4 +1,4 @@
-import BaseUrlLink from '@site/src/components/databaseDocs/baseLink';
+import BaseUrlLink from "@site/src/components/databaseDocs/baseLink";
 
 ## What's about to happen
 
@@ -17,10 +17,8 @@ metadata.
 :::
 
 <!-- prettier-ignore -->
-Hasura DDN uses a concept called "connector linking" to take [NDC-compliant](https://github.com/hasura/ndc-spec)
-configuration JSON files for a data connector and transform them into an `hml` (Hasura Metadata Language) file as a
-
-<BaseUrlLink to="/supergraph-modeling/data-connectors/" text="DataConnectorLink" /> metadata object.
+Hasura DDN uses a concept called "connector linking" to take configuration JSON files from a data connector and
+transform them into an  [NDC-compliant](https://github.com/hasura/ndc-spec) `hml` (Hasura Metadata Language) file as a <BaseUrlLink to="/supergraph-modeling/data-connector-links/" text="DataConnectorLink" /> metadata object.
 
 Basically, metadata objects in `hml` files define our API.
 
@@ -60,7 +58,7 @@ schema:
     functions: []
     procedures: []
   capabilities:
-    version: ''
+    version: ""
     capabilities:
       query: {}
       mutation: {}
@@ -496,7 +494,7 @@ schema:
             argument_type:
               type: named
               name: MinKey
-      'Null':
+      "Null":
         aggregate_functions:
           count:
             result_type:
@@ -509,7 +507,7 @@ schema:
             type: custom
             argument_type:
               type: named
-              name: 'Null'
+              name: "Null"
       ObjectId:
         representation:
           type: string
diff --git a/docs/getting-started/connect-to-data/_databaseDocs/_postgreSQL/_02-create-source-metadata.mdx b/docs/getting-started/connect-to-data/_databaseDocs/_postgreSQL/_02-create-source-metadata.mdx
index 30720826a..e9a213a5f 100644
--- a/docs/getting-started/connect-to-data/_databaseDocs/_postgreSQL/_02-create-source-metadata.mdx
+++ b/docs/getting-started/connect-to-data/_databaseDocs/_postgreSQL/_02-create-source-metadata.mdx
@@ -1,4 +1,4 @@
-import BaseUrlLink from '@site/src/components/databaseDocs/baseLink';
+import BaseUrlLink from "@site/src/components/databaseDocs/baseLink";
 
 ## What's about to happen?
 
@@ -19,7 +19,7 @@ our PostgreSQL database — to create metadata which Hasura can use to construct
 
 <!-- prettier-ignore -->
 Hasura DDN uses a concept called "connector linking" to take [NDC-compliant](https://github.com/hasura/ndc-spec)
-configuration JSON files for a data connector and transform them into an `hml` (Hasura Metadata Language) file as a <BaseUrlLink to="/supergraph-modeling/data-connectors/" text="DataConnectorLink" /> metadata object.
+configuration JSON files for a data connector and transform them into an `hml` (Hasura Metadata Language) file as a <BaseUrlLink to="/supergraph-modeling/data-connector-links/" text="DataConnectorLink" /> metadata object.
 
 Basically, metadata objects in `hml` files define our API.
 
@@ -57,7 +57,7 @@ schema:
     functions: []
     procedures: []
   capabilities:
-    version: ''
+    version: ""
     capabilities:
       query: {}
       mutation: {}