Fix double slashes in urls (aws-amplify#6418)

Co-authored-by: Katie Goines <[email protected]>

src/fragments/lib-v1/geo/ios/existing-resources.mdx

@@ -1,6 +1,6 @@
 ## In your app configuration
 
-Amplify Geo is dependent on your Amplify Auth category. If it is not already configured, then you will need to [configure it](/[platform]/prev/build-a-backend/auth//existing-resources) as well.
+Amplify Geo is dependent on your Amplify Auth category. If it is not already configured, then you will need to [configure it](/[platform]/prev/build-a-backend/auth/existing-resources) as well.
 
 Existing Amazon Location Service resources can be used with the Amplify Libraries by adding information about the resources to your `amplifyconfiguration.json` file.
 

src/pages/[platform]/build-a-backend/graphqlapi/set-up-graphql-api/index.mdx

@@ -57,7 +57,7 @@ Amplify's GraphQL API category can be deployed either using the [Amplify CLI](/[
 
 Pre-requisites:
 
-- The [Amplify CLI is installed and configured](/[platform]/tools/cli/start/set-up-cli//)
+- The [Amplify CLI is installed and configured](/[platform]/tools/cli/start/set-up-cli/)
 - Have an Amplify [project already initialized](/[platform]/tools/cli/start/key-workflows/#initialize-new-project)
 
 First, set up your GraphQL API by running:

src/pages/[platform]/tools/cli/project/troubleshooting/index.mdx

@@ -46,7 +46,7 @@ To debug deployment issues, it's helpful to understand the [file structure of yo
 To debug deployment issues in projects with GraphQL API, it's helpful to understand the various artifacts generated by Amplify in a GraphQL project.
 
 1. GraphQL schema VTL generation: The Amplify CLI GraphQL workflow uses the [AWS AppSync service](https://docs.aws.amazon.com/appsync/latest/devguide/system-overview-and-architecture.html) to provision the GraphQL API. The `amplify api gql-compile` command transpiles the GraphQL schema provided by the developer and generates all the artifacts required to deploy the API in AWS.
-   - Directives like [@model](/[platform]/build-a-backend/graphqlapi/data-modeling//), [@function](/[platform]/tools/cli-legacy/function-directive/), [@auth](/[platform]/build-a-backend/graphqlapi/customize-authorization-rules/), and [@searchable](/[platform]/build-a-backend/graphqlapi/search-and-result-aggregations/) in the GraphQL schema are used to generate CloudFormation and provision AWS resources.
+   - Directives like [@model](/[platform]/build-a-backend/graphqlapi/data-modeling/), [@function](/[platform]/tools/cli-legacy/function-directive/), [@auth](/[platform]/build-a-backend/graphqlapi/customize-authorization-rules/), and [@searchable](/[platform]/build-a-backend/graphqlapi/search-and-result-aggregations/) in the GraphQL schema are used to generate CloudFormation and provision AWS resources.
    - The GraphQL resolvers for Query, Mutation or Subscription are converted into [VTL (Velocity Template Language)](https://docs.aws.amazon.com/appsync/latest/devguide/resolver-mapping-template-reference-programming-guide.html) files. AWS AppSync uses VTL to translate GraphQL requests from clients into a request to your data source.
 1. GraphQL schema client-side code generation: The Amplify CLI GraphQL workflow allows developers to generate client-side code for web and mobile clients using the `amplify codegen` command. Read the [Amplify code generation documentation](/[platform]/build-a-backend/graphqlapi/client-code-generation/) prior to debugging any client-side code generation issues.