Merge pull request #10 from jacoblogan/update-cli-links

Update cli links

src/pages/cli-legacy/graphql-transformer/connection.mdx

@@ -9,7 +9,7 @@ export const meta = {
 
 The `@connection` directive enables you to specify relationships between `@model` types. Currently, this supports one-to-one, one-to-many, and many-to-one relationships. You may implement many-to-many relationships using two one-to-many connections and a joining `@model` type. See the usage section for details.
 
-[We also provide a fully working schema with 17 patterns related to relational designs](/cli/graphql-transformer/dataaccess).
+[We also provide a fully working schema with 17 patterns related to relational designs](/cli-legacy/graphql-transformer/dataaccess).
 
 ### Definition
 

src/pages/cli-legacy/graphql-transformer/key.mdx

@@ -214,4 +214,4 @@ If you're running into the error above during `amplify push`, it is likely that
 
 ## Combining @key with @connection
 
-Secondary indexes created with the `@key` directive can be used to resolve connections when creating relationships between types. To learn how this works, check out [the documentation for @connection](/cli/graphql-transformer/connection).
+Secondary indexes created with the `@key` directive can be used to resolve connections when creating relationships between types. To learn how this works, check out [the documentation for @connection](/cli-legacy/graphql-transformer/connection).

src/pages/cli-legacy/graphql-transformer/overview.mdx

@@ -207,7 +207,7 @@ amplify push
 
 The following schema updates require replacement of the underlying DynamoDB table:
 1. Removing or renaming a model
-2. Modifying the [primary key](/cli/graphql-transformer/key) of a model
+2. Modifying the [primary key](/cli-legacy/graphql-transformer/key) of a model
 3. Modifying a Local Secondary Index of a model (only applies to projects with [secondaryKeyAsGSI](/cli/reference/feature-flags/#secondaryKeyAsGSI) turned off)
 
 When trying to push a schema change with one or more of these updates you will see an error message explaining that you will lose ALL DATA in any table that requires replacement. To confirm you want to continue with the deployment, run:

src/pages/cli/reference/files.mdx

@@ -56,7 +56,7 @@ These files work together to maintain the overall state of the Amplify project s
 
 > Add to version control: YES
 
-The `backend-config.json` in the `backend` directory contains configuration about your project's backend, such as how connects to AWS resources (eg. Cognito for auth or AppSync for an API backend). Typically, this file is updated by the CLI commands like `amplify add auth` or `amplify add api`. It can also be [extended manually](/cli/usage/customcf) to configure your backend beyond Amplify CLI's features. Both the `amplify/backend` and `amplify/#current-cloud-backend` directories contain a `backend-config.json` file.
+The `backend-config.json` in the `backend` directory contains configuration about your project's backend, such as how connects to AWS resources (eg. Cognito for auth or AppSync for an API backend). Typically, this file is updated by the CLI commands like `amplify add auth` or `amplify add api`. It can also be [extended manually](/cli/custom/cloudformation) to configure your backend beyond Amplify CLI's features. Both the `amplify/backend` and `amplify/#current-cloud-backend` directories contain a `backend-config.json` file.
 
 ### amplify-meta.json
 
@@ -93,16 +93,15 @@ The metadata for each service is first logged into the meta file after the `ampl
 
 This file is generated only for JavaScript projects. It contains the consolidated outputs from all the categories and is placed under the `src` directory specified during the `init` process. It is updated after `amplify push`.
 
-This file is consumed by the [Amplify](https://github.com/aws-amplify/amplify-js) JavaScript library for configuration. It contains information which is non-sensitive and only required for external, unauthenticated actions from clients (such as user registration or sign-in flows in the case of Auth) or for constructing appropriate endpoint URLs after authorization has taken place. 
+This file is consumed by the [Amplify](https://github.com/aws-amplify/amplify-js) JavaScript library for configuration. It contains information which is non-sensitive and only required for external, unauthenticated actions from clients (such as user registration or sign-in flows in the case of Auth) or for constructing appropriate endpoint URLs after authorization has taken place.
 
 ### amplifyconfiguration.json
 
 > Manual edits okay: NO
 
 > Add to version control: NO
 
-This file is generated by Amplify CLI for Swift and Android projects. It contains the consolidated outputs from all the categories and is updated after `amplify push`.
-It is consumed by the [Amplify Swift](https://github.com/aws-amplify/amplify-swift/) and [Amplify Android](https://github.com/aws-amplify/amplify-android) libraries for configuration.
+This file is generated by Amplify CLI for Swift and Android projects. It contains the consolidated outputs from all the categories and is updated after `amplify push`. It is consumed by the [Amplify Swift](https://github.com/aws-amplify/amplify-swift/) and [Amplify Android](https://github.com/aws-amplify/amplify-android) libraries for configuration.
 
 Note: `amplifyconfiguration.json` is the equivalent of `aws-exports.js` generated for JavaScript projects.
 

src/pages/cli/teams/commands.mdx

@@ -48,7 +48,7 @@ The `add` command goes through the following steps:
 - Creates S3 bucket for deployment
 - Creates a new backend environment in [AWS Amplify Console](https://console.aws.amazon.com/amplify) to view and manage resources.
 
-Optionally, you can configure an IAM Permissions Boundary for all Amplify-generated roles via the `--permissions-boundary` parameter. For more information about configuring IAM Permissions Boundary, see [IAM Permissions Boundary for Amplify-generated roles](/cli/usage/permissions-boundary).
+Optionally, you can configure an IAM Permissions Boundary for all Amplify-generated roles via the `--permissions-boundary` parameter. For more information about configuring IAM Permissions Boundary, see [IAM Permissions Boundary for Amplify-generated roles](/cli/project/permissions-boundary).
 
 ### Pull the environment from the cloud