fixing some external links that should be internal references

content/en/getting-started/installation.md

@@ -303,7 +303,7 @@ $ docker-compose up
 - If using the Docker default bridge network using `network_mode: bridge`, container name resolution will not work inside your containers.
   Please consider removing it, if this functionality is needed.
 
-- To configure an auth token, refer to the [auth token](https://docs.localstack.cloud/getting-started/auth-token/) documentation.
+- To configure an auth token, refer to the [auth token]({{< ref "auth-token" >}}) documentation.
 {{< /alert >}}
 
 Please note that there are a few pitfalls when configuring your stack manually via docker-compose (e.g., required container name, Docker network, volume mounts, and environment variables).

content/en/tutorials/ecs-ecr-container-app/index.md

@@ -33,7 +33,7 @@ ECS tasks can pull container images from ECR repositories and are customizable u
 ## Prerequisites
 
 -   [LocalStack Pro](https://localstack.cloud/pricing/)
--   [awslocal](https://docs.localstack.cloud/integrations/aws-cli/#localstack-aws-cli-awslocal)
+-   [awslocal]({{< ref "aws-cli#localstack-aws-cli-awslocal" >}})
 -   [Docker](https://docker.io/)
 -   [`cURL`](https://curl.se/download.html)
 

content/en/tutorials/elb-load-balancing/index.md

@@ -37,7 +37,7 @@ In this tutorial we focus on the Application Load Balancer (ALB), which operates
 - LocalStack Pro
 - [Serverless framework](https://www.serverless.com/framework/docs/getting-started/)
 - [Node.js & `npm`](https://nodejs.org/en/download/)
-- [`awslocal`](https://docs.localstack.cloud/integrations/aws-cli/#localstack-aws-cli-awslocal)
+- [awslocal]({{< ref "aws-cli#localstack-aws-cli-awslocal" >}})
 - `cURL` & `jq`
 
 ## Setup a Serverless project

content/en/tutorials/java-notification-app/index.md

@@ -41,7 +41,7 @@ For this tutorial, you will need:
 
 - [LocalStack Pro](https://localstack.cloud/pricing/) to emulate the AWS services (SNS, SQS, SES, etc) locally
   - Don't worry, if you don't have a subscription yet, you can just get a trial license for free.
-- [awslocal](https://docs.localstack.cloud/integrations/aws-cli/#localstack-aws-cli-awslocal)
+- [awslocal]({{< ref "aws-cli#localstack-aws-cli-awslocal" >}})
 - [Docker](https://docker.io/)
 - Java 11+
 - Maven 3+

content/en/tutorials/lambda-ecr-container-images/index.md

@@ -34,7 +34,7 @@ leadimage: "lambda-ecr-container-images-featured-image.png"
 Before diving into this tutorial, make sure you have the following prerequisites:
 
 - LocalStack Pro
-- [`awslocal` CLI](https://docs.localstack.cloud/integrations/aws-cli/#localstack-aws-cli-awslocal)
+- [awslocal]({{< ref "aws-cli#localstack-aws-cli-awslocal" >}})
 - [Python](https://www.python.org/downloads/)
 - [Docker](https://docker.io/)
 

content/en/tutorials/reproducible-machine-learning-cloud-pods/index.md

@@ -44,7 +44,7 @@ We will then create a Cloud Pod to save the state of our LocalStack instance and
 For this tutorial, you will need the following:
 
 - [LocalStack Pro](https://localstack.cloud/pricing/)
-- [`awslocal` CLI](https://docs.localstack.cloud/integrations/aws-cli/#localstack-aws-cli-awslocal)
+- [awslocal]({{< ref "aws-cli#localstack-aws-cli-awslocal" >}})
 - [Optical recognition of handwritten digits dataset](https://archive.ics.uci.edu/ml/datasets/Optical+Recognition+of+Handwritten+Digits)
 
 If you don't have a subscription to LocalStack Pro, you can request a trial license upon sign-up. For this tutorial to work, you must have the LocalStack CLI installed, which must be version 1.3 or higher. The Cloud Pods CLI is shipped with the LocalStack CLI, so you don't need to install it separately.

content/en/tutorials/schema-evolution-glue-msk/index.md

@@ -25,7 +25,7 @@ leadimage: "schema-evolution-glue-msk-featured-image.png"
 
 [Apache Kafka](https://kafka.apache.org/) is an open-source distributed event store and stream-processing platform. It is used to capture data generated by producers and distribute it among its consumers. Kafka is known for its scalability, with reports of production environments scaling to [trillions of messages per day](https://engineering.linkedin.com/blog/2019/apache-kafka-trillion-messages). With [Amazon Managed Streaming for Apache Kafka (MSK)](https://aws.amazon.com/msk/), AWS provides a service to provision Apache Kafka clusters easily.
 
-[LocalStack Pro](https://app.localstack.cloud/) supports [Amazon Managed Streaming for Kafka (MSK)](https://docs.localstack.cloud/aws/managed-streaming-for-kafka/), which enables you to spin up Kafka clusters on your local machine and test the integration of your applications with Amazon MSK.
+[LocalStack Pro](https://app.localstack.cloud/) supports [Amazon Managed Streaming for Kafka (MSK)]({{< ref "managed-streaming-for-kafka" >}}), which enables you to spin up Kafka clusters on your local machine and test the integration of your applications with Amazon MSK.
 
 Kafka clusters are often used as the central messaging infrastructure in complex microservice environments.
 However, the continuous and independent development of the individual microservices - the data producers and consumers - can make it hard to coordinate and evolve data schemas over time without introducing application failures due to incompatibilities. A common solution to this problem is to use a schema registry which provides for the validation of schema changes, preventing any unsafe changes and subsequent application failures.
@@ -54,7 +54,7 @@ For this tutorial you will need:
 
 - [LocalStack Pro](https://localstack.cloud/pricing/) to emulate Amazon MSK and AWS Glue Schema Registry locally
   - Don't worry, if you don't have a subscription yet, you can just get a trial license for free.
-- [awslocal](https://docs.localstack.cloud/integrations/aws-cli/#localstack-aws-cli-awslocal)
+- [awslocal]({{< ref "aws-cli#localstack-aws-cli-awslocal" >}})
 - Java 11+
 - Maven 3
 

content/en/user-guide/ci/_index.md

@@ -21,7 +21,7 @@ Let's assume that your team has an automated CI workflow into which you want to
 
 {{< figure src="localstack-in-ci.svg" alt="An example CI/CD workflow using LocalStack" width="90%">}}
 
-The CI build is triggered by pushing code to a version control repository, like GitHub. The CI runner starts LocalStack and executes the test suite. You can also use the same Infrastructure-as-Code (IaC) configuration that you use to set up AWS in your production environment to set up LocalStack in the CI environment. You can also pre-seed state into the local AWS services (e.g., DynamoDB entries or S3 files) provided by LocalStack in your CI environment via [Cloud Pods](https://docs.localstack.cloud/tools/cloud-pods/).
+The CI build is triggered by pushing code to a version control repository, like GitHub. The CI runner starts LocalStack and executes the test suite. You can also use the same Infrastructure-as-Code (IaC) configuration that you use to set up AWS in your production environment to set up LocalStack in the CI environment. You can also pre-seed state into the local AWS services (e.g., DynamoDB entries or S3 files) provided by LocalStack in your CI environment via [Cloud Pods]({{< ref "user-guide/tools/cloud-pods" >}}).
 
 After a successful test run, you can execute the more expensive AWS CodeBuild pipeline for deploying your application. You can enrich the test reports created by your testing framework with traces and analytics generated inside LocalStack.