docs: fix broken links (aws#4252)

Resolves aws#4251


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the Apache 2.0 License.

site/content/docs/developing/svc-to-svc-communication.en.md

@@ -5,7 +5,7 @@
 [ECS Service Connect](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-connect.html) enables a client service to connect to its downstream services in a load-balanced and resilient fashion. Furthermore, it simplifies the way of exposing a service to its clients by specifying friendly aliases. With Service Connect in Copilot, each service you create is given the following private alias by default: `http://<your service name>`.
 
 !!! attention
- Service Connect is not yet supported for [Request-Driven Web Services](../docs/concepts/services.en.md#request-driven-web-service).
+ Service Connect is not yet supported for [Request-Driven Web Services](../concepts/services.en.md#request-driven-web-service).
 
 ### How do I use Service Connect?
 Imagine we have an app called `kudos` and two services: `api` and `front-end`, deployed in the same environment. In order to use Service Connect, both services' manifests need to have:

site/overrides/layouts/home.html

@@ -308,15 +308,15 @@
  <div class="md-main__inner">
  <div>
  <h1>Your toolkit for containerized applications on AWS</h1>
- <p>AWS Copilot is an open source command line interface that makes it easy for developers to <span class="em">build</span>, 
+ <p>AWS Copilot is an open source command line interface that makes it easy for developers to <span class="em">build</span>,
  <span class="em">release</span>, and <span class="em">operate</span> production ready containerized applications on AWS App Runner, Amazon ECS, and AWS Fargate.
  </p>
  <a
  href="docs/overview/"
  title="Get Started"
  class="md-button md-button--primary"
  >
- Get started 
+ Get started
  <svg width="11" height="10" viewBox="0 0 11 10" fill="none" style="margin-left:2px"><path d="M1 5.16772H9.5M9.5 5.16772L6.5 1.66772M9.5 5.16772L6.5 8.66772" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"></path></svg>
  </a>
  </div>
@@ -343,7 +343,7 @@ <h1>Your toolkit for containerized applications on AWS</h1>
  <h3>Get started with architectures</h3>
  <p>
  Run a <span class="em">single command</span> to quickly get started with a containerized
- application using best practices on AWS from a Dockerfile. 
+ application using best practices on AWS from a Dockerfile.
  </p>
  <p>
  Instead of modeling individual resources, Copilot provides common cloud architectures:
@@ -387,7 +387,7 @@ <h5>Manifests</h5>
  </a>
 
  <!-- Networking -->
- <a class="card-wrapper" href="docs/developing/service-discovery">
+ <a class="card-wrapper" href="docs/developing/svc-to-svc-communication">
  <div class="card">
  <div class="logo">
  <span class="twemoji">
@@ -431,7 +431,7 @@ <h3>Continuous delivery</h3>
  <p>
  No need to worry about gluing Copilot commands in a script to create an automated release process.
  Copilot provides commands to create multiple deployment <a href="docs/concepts/environments/">environments</a> in separate AWS accounts and regions,
- as well as creating an AWS CodePipeline <a href="docs/concepts/pipelines/">pipeline</a> to build your container images, deploy your services, and 
+ as well as creating an AWS CodePipeline <a href="docs/concepts/pipelines/">pipeline</a> to build your container images, deploy your services, and
  run automated tests.
  </p>
  </div>
@@ -509,7 +509,7 @@ <h5>Automated releases</h5>
  <div class="first-column">
  <h3>Operations is part of the workflow</h3>
  <p>
- Modeling, provisioning, and deploying services are only part of the application lifecycle for the developer. 
+ Modeling, provisioning, and deploying services are only part of the application lifecycle for the developer.
  Copilot also supports workflows around troubleshooting and debugging to help when things go wrong. <a href="docs/commands/svc-logs/">Tail
  your logs</a>, <a href="docs/commands/svc-exec">get a shell</a> to a running container, <a href="docs/commands/svc-status/">view the health</a> of your services
  from the comfort of your terminal.