Anya/connections

docs/getting-started/getting-started-with-low-code-sql.md

@@ -69,9 +69,9 @@ Once, the token is generated copy and save it from **(5) Token** and you’re go
 
 ### 2.3 Setup Prophecy’s Fabric
 
-Prophecy introduces the concept of a Fabric to describe an execution environment. In this case, we create a single Fabric to connect a Databricks cluster or warehouse, execute SQL models interactively, and deploy scheduled Jobs. The Fabric defines the environment where SQL tables and views are materialized. Typically you should setup at least one Fabric each for development and production environments. Use the development environment(Fabric) for quick ad-hoc building purposes with only sample data and use the production environment for daily runs with real data for your use case.
+Prophecy introduces the concept of a Fabric to describe an execution environment. In this case, we create a single Fabric to connect a Databricks cluster or warehouse, execute SQL models interactively, and deploy scheduled Jobs. The Fabric defines the environment where SQL tables and views are materialized. Typically you should setup at least one Fabric each for development and production environments. Use the development environment (Fabric) for quick ad-hoc building purposes with only sample data and use the production environment for daily runs with real data for your use case.
 
-You can read more about Fabrics [here.](https://docs.prophecy.io/concepts/fabrics/create-a-fabric/)
+You can read more about Fabrics [here.](/docs/concepts/fabrics/fabrics.md)
 
 ![Create Fabric](img/2-4-create-fabric.png)
 
@@ -87,11 +87,11 @@ Enter the **(3) JDBC Url** and **(4) Personal Access Token** gathered from the p
 
 Click **(7) Complete** when finished. Prophecy checks the credentials and details for network and catalog accesses. If either fails, the Fabric won’t be created and you will receive an Exception error.
 
-Please note, Fabrics are owned by Teams. Every Member present within the Team will be able to access the Fabric, however, each individual has to provide their own Personal Access Token!
+Please note, Fabrics are owned by Teams. Every Member present within the Team will be able to access the Fabric, however, each individual has to provide their own Personal Access Token.
 
 ## 3. Create a new Project
 
-Prophecy’s Project is a Git repository or a directory on Git that contains all of your transformation logic. Each Prophecy Project contains a dbt Core™️ project. Learn more about Projects [here.](https://docs.prophecy.io/concepts/project)
+Prophecy’s Project is a Git repository or a directory on Git that contains all of your transformation logic. Each Prophecy Project contains a dbt Core™️ project. Learn more about Projects [here.](/docs/concepts/project/project.md)
 
 After Fabric creation you can see one project initialized for you by default called HelloWorld_SQL. If you just want to play around with Prophecy, you can start there. However, for the purpose of this tutorial we’re going to build a brand new project from scratch.
 
@@ -111,9 +111,9 @@ If you’re new to Git, we recommend starting by connecting to Prophecy Managed
 
 ### 3.1. Connect to Prophecy Managed Git
 
-When choosing, Prophecy Managed Git as your default Git repository, there’s no further steps required! Prophecy automatically takes care of repository creation, connection, and initialization. You can just click **(3) Continue** to finalize the project setup.
+When choosing Prophecy Managed Git as your default Git repository, there are no further steps required! Prophecy automatically takes care of repository creation, connection, and initialization. You can just click **(3) Continue** to finalize the project setup.
 
-Using Prophecy Managed Git is very easy, but has some major downsides and therefore not recommended for production use-cases. Primarily, you will not be able to access the repository externally from Prophecy programmatically (which is a common enterprise requirement) or create [Pull Requests](https://docs.prophecy.io/metadata/pr-templates/#raising-pull-requests) (which is also recommended as a part of standard [Git flow](https://docs.github.com/en/get-started/quickstart/github-flow)).
+Using Prophecy Managed Git is very easy, but has some major downsides and therefore not recommended for production use-cases. Primarily, you will not be able to access the repository externally from Prophecy programmatically (which is a common enterprise requirement) or create [Pull Requests](/docs/metadata/pull-request-templates.md/#raising-pull-requests) (which is also recommended as a part of standard [Git flow](https://docs.github.com/en/get-started/quickstart/github-flow)).
 
 If you decide to choose this option, you can always migrate the project to an external Git Repository by cloning it.
 

docs/low-code-spark/configuration/conditional-execution.md

@@ -45,6 +45,6 @@ Unlike pass-through conditions, removal conditions can be applied to any Gem in
 
 Currently, SetOperations and Script Gems in the Pipeline are capable of handling missing inputs. For other Gems, if any input is missing, the Gem will be removed along with all downstream transformations. The same behavior applies to subgraphs as well.
 
-To modify the handling of missing inputs in other Gems, users can update the Gem specs in the [Gem Builder](./../extensibility/gem-builder) by adding a boolean parameter called allInputsRequired. By setting this parameter to true or false, users can determine whether a em should be removed if any of its inputs are missing.
+To modify the handling of missing inputs in other Gems, users can update the Gem specs in the [Gem Builder](/docs/package-hub/package-builder/gem-builder.md) by adding a boolean parameter called allInputsRequired. By setting this parameter to true or false, users can determine whether a Gem should be removed if any of its inputs are missing.
 
 This customization option allows users to tailor the behavior of the Pipeline and the handling of missing data based on their specific requirements.

docs/package-hub/package-builder/ShareableSubgraphs.md

@@ -38,7 +38,7 @@ Please see this video for an example
 
 ## Sharing Subgraphs Across Projects
 
-Once a Project (let's call it _BaseProject_) is Released and added as a [Dependency]((/docs/package-hub/package-hub.md#use-a-package) to another Project(let's call it _AppProject_), all Subgraphs from _BaseProject_ are available in all Pipelines of _AppProject_.
+Once a Project (let's call it _BaseProject_) is Released and added as a [Dependency](/docs/package-hub/package-hub.md#Use-a-package) to another Project(let's call it _AppProject_), all Subgraphs from _BaseProject_ are available in all Pipelines of _AppProject_.
 
 Please see this video for an example
 

docs/package-hub/package-builder/package-builder.md

@@ -7,7 +7,7 @@ tags: []
 
 With **Package Builder**, engineering teams gain an intuitive tool for standardized creation of packaged operations, including Pipelines, Functions, Custom Gems, and more. You can now easily reuse code and enforce best practices across your data operations, eliminating manual and error-prone processes.
 
-Create a Project with any combination of building blocks below. For example, the [custom Gem page](/docs/package-hub/package-builder/gem-builder.md) has detailed instructions on building a custom Gem within a Project. When you commit and release your Project with a version, you are now able to share the released Project as a **Package** dependency. Other teams can then re-use the components. Check out the [Package Hub](/docs/package-hub/package-hub.md) page for a deep dive on using Packages.
+Create a Project with any combination of building blocks below. For example, the [Build Shareable Gems page](/docs/package-hub/package-builder/gem-builder.md) has detailed instructions on building a custom Gem within a Project. When you commit and release your Project with a version, you are now able to share the released Project as a **Package** dependency. Other teams can then re-use the components. Check out the [Package Hub](/docs/package-hub/package-hub.md) page for a deep dive on using Packages.
 
 ## Build shareable components