[en] Update links in 'content/en'

content/en/abstraction.md

@@ -4,7 +4,7 @@ status: Completed
 category: Property
 ---
 
-In the context of computing, an abstraction is a representation that hides specifics from a consumer of [services](https://glossary.cncf.io/service/) (a consumer being a computer program or human), making a system more generic and thus easily understood. A good example is your laptop's operating system (OS). It abstracts away all the details of how your computer works. You don't need to know anything about CPU, memory, and how programs are handled, you just operate the OS and the OS deals with the details. All these details are hidden behind the OS "curtain" or abstraction. 
+In the context of computing, an abstraction is a representation that hides specifics from a consumer of [services](/service/) (a consumer being a computer program or human), making a system more generic and thus easily understood. A good example is your laptop's operating system (OS). It abstracts away all the details of how your computer works. You don't need to know anything about CPU, memory, and how programs are handled, you just operate the OS and the OS deals with the details. All these details are hidden behind the OS "curtain" or abstraction. 
 
 Systems typically have multiple abstraction layers. This significantly simplifies development. When programming, developers build components compatible with a particular abstraction layer and don't have to worry about all underlying specifics that can be very heterogeneous. If it works with the abstraction layer, it works with the system — no matter what's under the hood. 
 

content/en/chaos_engineering.md

@@ -5,10 +5,10 @@ category: concept
 ---
 
 ## What it is
-Chaos Engineering or CE is the discipline of experimenting on a [distributed system](https://glossary.cncf.io/distributed_systems/) in production to build confidence in the system's capability to withstand turbulent and unexpected conditions.
+Chaos Engineering or CE is the discipline of experimenting on a [distributed system](/distributed_systems/) in production to build confidence in the system's capability to withstand turbulent and unexpected conditions.
 
 ## Problem it addresses
-[SRE](https://glossary.cncf.io/site_reliability_engineering/) and [DevOps](https://glossary.cncf.io/devops/) practices focus on techniques to increase product resiliency and [reliability](https://glossary.cncf.io/reliability/). A system's ability to tolerate failures while ensuring adequate service quality is typically a software development requirement. There are several aspects involved that could lead to outages of an application, like infrastructure, platform or other moving parts of a ([microservice](https://glossary.cncf.io/microservices/)-based) application. High-frequency deployment of new features to the production environment can result in a high probability of downtime and a critical incident — with considerable consequences to the business.
+[SRE](/site_reliability_engineering/) and [DevOps](/devops/) practices focus on techniques to increase product resiliency and [reliability](/reliability/). A system's ability to tolerate failures while ensuring adequate service quality is typically a software development requirement. There are several aspects involved that could lead to outages of an application, like infrastructure, platform or other moving parts of a ([microservice](/microservices/)-based) application. High-frequency deployment of new features to the production environment can result in a high probability of downtime and a critical incident — with considerable consequences to the business.
 
 ## How it helps
 Chaos engineering is a technique to meet resilience requirements. It is used to achieve resilience against infrastructure, platform, and application failures. Chaos engineers use chaos experiments to proactively inject random failures to verify that an application, infrastructure, or platform can self-heal and the failure cannot noticeably impact customers. Chaos experiments aim to discover blind spots (e.g. monitoring or autoscaling techniques) and to improve the communications between teams during critical incidents. This approach helps increase resiliency and the team's confidence in complex systems, particularly production.

content/en/containers_as_a_service.md

@@ -7,7 +7,7 @@ category: Technology
 ## What it is
 Containers-as-a-Service (CaaS) is a cloud service that helps manage and deploy apps using [container](/container/)-based [abstraction](/abstraction/). This service can be deployed on-premises or in the cloud. 
 
-CaaS providers offer a framework or orchestration platform that automates key IT functions on which containers are deployed and managed. It helps developers build secure and [scalable](/scalibility/) containerized apps. Because users only buy the resources they need (scheduling capabilities, load balancing, etc.), they save money and increase efficiency. Containers create consistent environments to rapidly develop and deliver [cloud-native applications](/cloud_native_apps/) that can run anywhere. 
+CaaS providers offer a framework or orchestration platform that automates key IT functions on which containers are deployed and managed. It helps developers build secure and [scalable](/scalability/) containerized apps. Because users only buy the resources they need (scheduling capabilities, load balancing, etc.), they save money and increase efficiency. Containers create consistent environments to rapidly develop and deliver [cloud-native applications](/cloud_native_apps/) that can run anywhere. 
 
 ## Problem it addresses
 Without CaaS, software development teams need to deploy, manage, and monitor the underlying infrastructure that containers run on. 

content/en/contribute/_index.md

@@ -39,7 +39,7 @@ Once they assign it to you, you can start working on it. For the next steps, ple
 ## Propose new terms
 You can propose a new term for others to work on or create a new definition yourself. Either way, you'll start by creating an issue.
 
-Below is a step-by-step guide for those not yet familiar with GitHub. **If you are a GitHub Pro**, please *do* have a quick look to make sure you use our issue templates, appropriate naming conventions, claim a PR on Slack (otherwise we may miss it), and where to find the file template. And please make sure to read the [Style Guide](https://glossary.cncf.io/style-guide/) before getting started — thank you! 
+Below is a step-by-step guide for those not yet familiar with GitHub. **If you are a GitHub Pro**, please *do* have a quick look to make sure you use our issue templates, appropriate naming conventions, claim a PR on Slack (otherwise we may miss it), and where to find the file template. And please make sure to read the [Style Guide](/style-guide/) before getting started — thank you! 
 
 ### Creating an issue
 Go to the [Glossary GitHub repo](https://github.com/cncf/glossary/issues) issues and click on "new issue."
@@ -62,7 +62,7 @@ Note that you can only claim one term at a time. If you want to work on multiple
 
 ### Submitting a new term (creating a PR)
 
-Before getting started, please read the [Style Guide](https://glossary.cncf.io/style-guide/) — it will help minimize backs and forth. As stated in the style guide, we highly recommend starting with a Google or Word doc. 
+Before getting started, please read the [Style Guide](/style-guide/) — it will help minimize backs and forth. As stated in the style guide, we highly recommend starting with a Google or Word doc. 
 
 Once the term is ready to submit, go to content (under code)…
 

content/en/contributor-ladder/_index.md

@@ -20,7 +20,7 @@ There are a variety of ways you can contribute to the project, including:
 - **Helpers**: anyone who helps others on GitHub, Slack, or wherever community members need support,
 - **Ambassadors**: anyone who helps spread the word, educates the community on how to contribute and why they should do so. 
 
-Contributors can have multiple roles or focus on one area only. **All these contributions are equally important** and help foster a thriving community. Please refer to the [How to Contribute](https://glossary.cncf.io/contribute/) and [Style Guide](https://glossary.cncf.io/style-guide/) for content and localization contributions.
+Contributors can have multiple roles or focus on one area only. **All these contributions are equally important** and help foster a thriving community. Please refer to the [How to Contribute](/contribute/) and [Style Guide](/style-guide/) for content and localization contributions.
 
 ## 2. Approvers
 

content/en/database_as_a_service.md

@@ -6,7 +6,7 @@ category: Technology
 
 ## What it is
 
-Database-as-a-Service (DBaaS) is a service managed by a [cloud](https://glossary.cncf.io/cloud_computing/) operator (public or private) that supports applications without requiring the application team to perform traditional database administration functions. DBaaS allows app developers to leverage databases without being experts or hiring a database administrator (DBA) to keep the database up to date.
+Database-as-a-Service (DBaaS) is a service managed by a [cloud](/cloud_computing/) operator (public or private) that supports applications without requiring the application team to perform traditional database administration functions. DBaaS allows app developers to leverage databases without being experts or hiring a database administrator (DBA) to keep the database up to date.
 
 ## Problem it addresses 
 

content/en/distributed_apps.md

@@ -14,5 +14,5 @@ An application running on one single computer represents a single point of failu
 
 ## How it helps
 
-When splitting an application into different pieces and running them in many places, the overall system can tolerate more failures. It also allows an application to take advantage of scaling features not available to a single application instance, namely the ability to [scale horizontally](/horizontal-scaling/). This does, however, come at a cost: increased complexity and operational overhead — you’re now running lots of application components instead of one app.
+When splitting an application into different pieces and running them in many places, the overall system can tolerate more failures. It also allows an application to take advantage of scaling features not available to a single application instance, namely the ability to [scale horizontally](/horizontal_scaling/). This does, however, come at a cost: increased complexity and operational overhead — you’re now running lots of application components instead of one app.
 

content/en/function_as_a_service.md

@@ -5,10 +5,10 @@ category: Technology
 ---
 
 ## What it is
-Function as a Service (FaaS) is a type of [serverless](https://glossary.cncf.io/serverless/) [cloud computing](https://glossary.cncf.io/cloud_computing/) [service](https://glossary.cncf.io/service/) that allows executing code in response to events without maintaining the complex infrastructure typically associated with building and launching [microservices](https://glossary.cncf.io/microservices/) applications. With FaaS, users manage only functions and data while the cloud provider manages the application. This allows developers to get the functions they need without paying for services when code isn’t running. Some popular FaaS examples include: [Amazon's AWS Lambda](https://aws.amazon.com/lambda/), [Google Cloud Functions](https://cloud.google.com/functions/) and [Microsoft Azure Functions](https://azure.microsoft.com/en-us/services/functions/).   
+Function as a Service (FaaS) is a type of [serverless](/serverless/) [cloud computing](/cloud_computing/) [service](/service/) that allows executing code in response to events without maintaining the complex infrastructure typically associated with building and launching [microservices](/microservices/) applications. With FaaS, users manage only functions and data while the cloud provider manages the application. This allows developers to get the functions they need without paying for services when code isn’t running. Some popular FaaS examples include: [Amazon's AWS Lambda](https://aws.amazon.com/lambda/), [Google Cloud Functions](https://cloud.google.com/functions/) and [Microsoft Azure Functions](https://azure.microsoft.com/en-us/services/functions/).   
 
 ## Problem it addresses
-In a traditional on-premises scenario, a business manages and maintains its own data center. The business must invest in servers, storage, software, and other technologies and potentially hire an IT staff or contractors to purchase, manage, and upgrade all the equipment and licenses. The data center has to be built to meet peak demand, even when workloads decline and those resources stand idle. Conversely, if the business grows quickly, the IT department might struggle to keep up. Under a standard [Infrastructure-as-a-Service (IaaS)](https://glossary.cncf.io/infrastructure_as_a_service/) cloud computing model, users pre-purchase capacity units, meaning you pay a public cloud provider for always-on server components to run your apps. It’s the user’s responsibility to scale up server capacity during times of high demand and scale down when that capacity is no longer needed. The cloud infrastructure necessary to run an app is active even when the app isn’t being used.
+In a traditional on-premises scenario, a business manages and maintains its own data center. The business must invest in servers, storage, software, and other technologies and potentially hire an IT staff or contractors to purchase, manage, and upgrade all the equipment and licenses. The data center has to be built to meet peak demand, even when workloads decline and those resources stand idle. Conversely, if the business grows quickly, the IT department might struggle to keep up. Under a standard [Infrastructure-as-a-Service (IaaS)](/infrastructure_as_a_service/) cloud computing model, users pre-purchase capacity units, meaning you pay a public cloud provider for always-on server components to run your apps. It’s the user’s responsibility to scale up server capacity during times of high demand and scale down when that capacity is no longer needed. The cloud infrastructure necessary to run an app is active even when the app isn’t being used.
 
 ## How it helps
-FaaS gives developers an [abstraction](https://glossary.cncf.io/abstraction/) for running web applications in response to events without managing servers. For example, uploading a file could trigger custom code that transcodes the file into various formats. FaaS infrastructure will auto-scale the code for heavy use, and the developer does not have to spend any time or resources building the code for [scalability](https://glossary.cncf.io//scalability/). Billing is based on computation time alone, which means businesses do not have to pay when the functions are not in use.
+FaaS gives developers an [abstraction](/abstraction/) for running web applications in response to events without managing servers. For example, uploading a file could trigger custom code that transcodes the file into various formats. FaaS infrastructure will auto-scale the code for heavy use, and the developer does not have to spend any time or resources building the code for [scalability](//scalability/). Billing is based on computation time alone, which means businesses do not have to pay when the functions are not in use.

content/en/mTLS (Mutual Transport Layer Security).md

@@ -5,10 +5,10 @@ category: Concept
 ---
 
 ## What it is
-Mutual TLS (mTLS) is a technique used to authenticate and encrypt messages sent between two [services](https://glossary.cncf.io/service/). Mutual TLS is the standard [Transport Layer Security](https://glossary.cncf.io/tlstransport-layer-security/) (TLS) protocol but, instead of validating the identity of just one connection, both sides are validated.
+Mutual TLS (mTLS) is a technique used to authenticate and encrypt messages sent between two [services](/service/). Mutual TLS is the standard [Transport Layer Security](/tlstransport-layer-security/) (TLS) protocol but, instead of validating the identity of just one connection, both sides are validated.
 
 ## Problem it addresses
-[Microservices](https://glossary.cncf.io/microservices/) communicate over a network and, just like your wifi network, communication in transit over that network can be hacked. mTLS ensures that no unauthorized party can listen in on or impersonate legitimate requests.
+[Microservices](/microservices/) communicate over a network and, just like your wifi network, communication in transit over that network can be hacked. mTLS ensures that no unauthorized party can listen in on or impersonate legitimate requests.
 
 ## How it helps
 mTLS ensures that traffic is secure and trusted in both directions between a client and server, providing an additional layer of security for users who log in to a network or applications. It also verifies connections with client devices that do not follow a login process, such as Internet of Things (IoT) devices. Attacks like on-path attacks, spoofing attacks, credential stuffing, brute force attacks, etc. can be prevented by mTLS.

content/en/monolithic_apps.md

@@ -8,7 +8,7 @@ category: concept
 A monolithic application contains all functionality in a single deployable program. This is often the simplest and easiest place to start when making an application. However, once the application grows in complexity, monoliths can become hard to maintain. With more developers working on the same codebase, the likelihood of conflicting changes and the need for interpersonal communication between developers increases.
 
 ## Problem it Addresses
-Devolving an application into [microservices](https://glossary.cncf.io/microservices/) increases its operational overhead — there are more things to test, deploy, and keep running. Early in a product’s lifecycle, it may be advantageous to defer this complexity and build a monolithic application until the product is determined successful.
+Devolving an application into [microservices](/microservices/) increases its operational overhead — there are more things to test, deploy, and keep running. Early in a product’s lifecycle, it may be advantageous to defer this complexity and build a monolithic application until the product is determined successful.
 
 ## How it Helps
 A well-designed monolith can uphold lean principles by being the simplest way to get an application up and running. When the business value of the monolithic application proves successful, it can be decomposed into microservices. Crafting a microservices-based app before it has proven valuable may be premature spending of engineering effort. If the application yields no value, that effort becomes wasted.