fixed broken glide links (#316)

docs/glide/configuration/access-rules.md

@@ -67,7 +67,7 @@ Select from the options and then press **Next**.
 
 ![](/img/access-rules/02-provider.png)
 
-For detailed setup instructions on how to configure an AWS SSO provider with Organizational Units, Accounts and Permission Sets refer to [Organizational Unit Access](/common-fate/providers/registry/commonfate/aws-sso/usage/v2).
+For detailed setup instructions on how to configure an AWS SSO provider with Organizational Units, Accounts and Permission Sets refer to [Organizational Unit Access](/glide/providers/registry/commonfate/aws-sso/usage/v2).
 
   </TabItem>
   <TabItem value="okta" label="Okta">

docs/glide/configuration/updating.md

@@ -8,7 +8,7 @@ Release information, including the latest version number and the changelog, can
 
 The below process will use an example version upgrade from `v0.2.0` to `v0.2.1`.
 
-First, ensure that your `gdeploy` CLI is up to date. You can update the CLI by following the installation instructions [here](/common-fate/deploying-glide/setup).
+First, ensure that your `gdeploy` CLI is up to date. You can update the CLI by following the installation instructions [here](/glide/deploying-glide/setup).
 
 Edit your `deployment.yml` file as follows to specify the latest version:
 

docs/glide/deploying-glide/00-deploying-common-fate.md

@@ -6,11 +6,11 @@ slug: deploying-common-fate
 
 ## Quickstart
 
-This page is a quickstart guide for setting up a basic Glide deployment in 5 minutes. If you've got more than 5 minutes, head over to the [Prerequisites](/common-fate/deploying-glide/prerequisites) page to read the full guide.
+This page is a quickstart guide for setting up a basic Glide deployment in 5 minutes. If you've got more than 5 minutes, head over to the [Prerequisites](/glide/deploying-glide/prerequisites) page to read the full guide.
 
 All you need is an AWS account, an AWS profile that has the ability to create resources and IAM roles, and an internet connection. You'll only need to run a few commands. Note that while Glide requires AWS to host your deployment, your actual Access Providers can also be Azure or Okta based.
 
-First you'll install `gdeploy`, our command-line interface tool for managing Glide deployments. (not on Mac? [here's](/common-fate/deploying-glide/setup#installing-gdeploy) how you install `gdeploy` on other systems)
+First you'll install `gdeploy`, our command-line interface tool for managing Glide deployments. (not on Mac? [here's](/glide/deploying-glide/setup#installing-gdeploy) how you install `gdeploy` on other systems)
 
 ```
 brew install common-fate/granted/gdeploy
@@ -48,4 +48,4 @@ Once that's done, you should see this:
 
 Congrats! You've now 10x'd deploying Glide. If you want more details on what just happened, check out the subpages of this _Deploying Glide_ section.
 
-To start using Granted, check out adding [Access Providers](/common-fate/providers/providers).
+To start using Granted, check out adding [Access Providers](/glide/providers/providers).

docs/glide/deploying-glide/04-next-steps.md

@@ -8,9 +8,9 @@ slug: next-steps
 
 Before using Glide with your team, we recommend completing the following steps:
 
-1. [Configure Access Providers](/common-fate/providers/providers)
-2. [Enable SSO and user directory sync](/common-fate/sso/sso-setup)
-3. [Enable Slack notifications](/common-fate/configuration/slack)
-4. [Use a custom domain for the web portal](/common-fate/configuration/custom-domain)
+1. [Configure Access Providers](/glide/providers/providers)
+2. [Enable SSO and user directory sync](/glide/sso/sso-setup)
+3. [Enable Slack notifications](/glide/configuration/slack)
+4. [Use a custom domain for the web portal](/glide/configuration/custom-domain)
 
 If you use a [SIEM](https://en.wikipedia.org/wiki/Security_information_and_event_management) to collect security logs, you can connect Glide to it to capture audit trail events.

docs/glide/introduction.md

@@ -20,4 +20,4 @@ Glide key benefits are:
 
 ## Get started
 
-Follow the [Deployment guide](/common-fate/deploying-glide/deploying-common-fate/) to get your own instance of Glide up and running.
+Follow the [Deployment guide](/glide/deploying-glide/deploying-common-fate/) to get your own instance of Glide up and running.

docs/glide/providers/built-in/aws-sso/v2/usage.md

@@ -7,7 +7,7 @@
 Glide has support for AWS Organzational Unit (OU) access control. This allows you to grant access to a set of accounts based on the OU structure of your AWS organization.
 
 :::info
-To use this feature you must have a `commonfate/aws-sso` provider configured. See [AWS SSO Provider](/common-fate/providers/aws-sso/aws-sso) for more information.
+To use this feature you must have a `commonfate/aws-sso` provider configured. See [AWS SSO Provider](/glide/providers/aws-sso/aws-sso) for more information.
 :::
 
 ## What are Organizational Units?

docs/glide/sso/00-sso-setup.md

@@ -51,6 +51,6 @@ The SSO provider to deploy with  [Use arrows to move, type to filter]
 
 As part of setting up SSO and user directory sync, you'll be prompted for parameters to connect to your identity provider. Follow the guides below based on your corporate identity provider:
 
-- [Google Workspace](/common-fate/sso/google)
-- [Okta](/common-fate/sso/okta)
-- [Azure](/common-fate/sso/azure)
+- [Google Workspace](/glide/sso/google)
+- [Okta](/glide/sso/okta)
+- [Azure](/glide/sso/azure)

docs/glide/sso/updating-configuration.md

@@ -15,7 +15,7 @@ Enter 'y' and press enter.
 
 ```
 [i] Updating configuration for <your_identity_provider>
-[i] You can follow our <your_identity_provider> setup guide at: https://docs.commonfate.io/common-fate/sso/<your_identity_provider> for detailed instruction on setting up SSO
+[i] You can follow our <your_identity_provider> setup guide at: https://docs.commonfate.io/glide/sso/ <your_identity_provider> for detailed instruction on setting up SSO
 ```
 
 Next you can update or use the existing values for your provider. You will be prompted to enter each one.
@@ -50,6 +50,6 @@ This will prompt you to confirm your intent to disable current identity provider
 
 You should see a message like above.
 
-2. Next, run `gdeploy identity sso enable` to add new sets of configuration. Follow [this link](/common-fate/sso/sso-setup/#setting-up-sso) for more instruction on setting up SSO.
+2. Next, run `gdeploy identity sso enable` to add new sets of configuration. Follow [this link](/glide/sso/sso-setup/#setting-up-sso) for more instruction on setting up SSO.
 
 3. Finally, run `gdeploy update` to apply the changes to your CloudFormation deployment.