[en] Update links to 'microservices' (#3009)

Signed-off-by: Jihoon Seo <jihoon.seo@etri.re.kr>
Signed-off-by: Nate W <natew@cncf.io>
Co-authored-by: Nate W <natew@cncf.io>

content/en/application-programming-interface.md

@@ -21,4 +21,4 @@ Without a shared framework, it is challenging for applications to [scale](/scala
 
 APIs allow computer programs or applications to interact and share information in a defined and understandable manner. 
 They are the building blocks for modern applications and they provide developers with a way to integrate applications together. 
-Whenever you hear about [microservices](/microservices/) working together, you can infer that they interact via an API. 
+Whenever you hear about [microservices](/microservices-architecture/) working together, you can infer that they interact via an API. 

content/en/chaos-engineering.md

@@ -15,7 +15,7 @@ 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. 
+like infrastructure, platform or other moving parts of a ([microservice](/microservices-architecture/)-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.

content/en/distributed-apps.md

@@ -6,7 +6,7 @@ tags: ["architecture", "", ""]
 ---
 
 A distributed application is an application where the functionality is broken down into multiple smaller independent parts. 
-Distributed applications are usually composed of individual [microservices](/microservices/) 
+Distributed applications are usually composed of individual [microservices](/microservices-architecture/) 
 that handle different concerns within the broader application. 
 In a cloud native environment, the individual components typically run as [containers](/container/) on a [cluster](/cluster/). 
 

content/en/firewall.md

@@ -13,7 +13,7 @@ Firewalls can be hardware, software, or a combination of the two.
 
 By default, a network will allow anyone to enter and depart as long as they follow the network's routing rules. 
 Because of this default behavior, securing a network is challenging. 
-For example, in a [microservices](/microservices/)-based banking app, the services communicate with one another 
+For example, in a [microservices](/microservices-architecture/)-based banking app, the services communicate with one another 
 by transmitting highly sensitive financial data through their network. 
 A malicious actor may infiltrate the network, intercept communication, and do damage if there was no firewall in place.
 

content/en/function-as-a-service.md

@@ -5,7 +5,6 @@ category: Technology
 tags: ["infrastructure", "", ""]
 ---
 
-
 Function as a Service (FaaS) is a cloud computing model that provides a platform for executing event-triggered functions, allowing for automatic scaling without manual intervention.
 At its essence, FaaS enables the deployment of individual functions that are activated by specific events, operate on a short-term basis, and then shut down, ensuring resources are not wasted.
 This model supports an [autoscaling](/auto-scaling/) feature, enabling a function instance to be initiated per request and terminated post-execution, emphasizing its stateless nature.

content/en/load-balancer.md

@@ -6,7 +6,7 @@ tags: ["infrastructure", "networking", ""]
 ---
 
 A load balancer is a tool that efficiently distributes incoming requests among multiple instances of an application. 
-Take a [microservice](/microservices/) architecture for example, where each service can be [scaled horizontally](/horizontal-scaling/). 
+Take a [microservice](/microservices-architecture/) architecture for example, where each service can be [scaled horizontally](/horizontal-scaling/). 
 A load balancer sits in front of a scaled microservice and ensures that no one instance gets the bulk of the requests.
 Load balancers can be software or hardware-based.
 

content/en/loosely-coupled-architecture.md

@@ -8,7 +8,7 @@ tags: ["fundamental", "architecture", "property"]
 Loosely coupled architecture is an architectural style 
 where the individual components of an application are built independently from one another 
 (the opposite paradigm of [tightly coupled architectures](/tightly-coupled-architectures/)). 
-Each component, sometimes referred to as a [microservice](/microservices/), is built to perform a specific function 
+Each component, sometimes referred to as a [microservice](/microservices-architecture/), is built to perform a specific function 
 in a way that can be used by any number of other services. 
 This pattern is generally slower to implement than tightly coupled architecture 
 but has a number of benefits, particularly as applications scale.

content/en/monolithic-apps.md

@@ -13,7 +13,7 @@ the likelihood of conflicting changes and the need for interpersonal communicati
 
 ## Problem it Addresses
 
-Devolving an application into [microservices](/microservices/) increases its operational overhead 
+Devolving an application into [microservices](/microservices-architecture/) 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.

content/en/mutual-transport-layer-security.md

@@ -11,7 +11,7 @@ instead of validating the identity of just one connection, both sides are valida
 
 ## Problem it addresses
 
-[Microservices](/microservices/) communicate over a network and, 
+[Microservices](/microservices-architecture/) 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.
 

content/en/platform-as-a-service.md

@@ -11,7 +11,7 @@ Heroku, Cloud Foundry, App Engine are examples of PaaS offerings.
 
 ## Problem it addresses
 
-To take advantage of cloud native patterns like [microservices](/microservices/) or [distributed applications](/distributed-apps/), 
+To take advantage of cloud native patterns like [microservices](/microservices-architecture/) or [distributed applications](/distributed-apps/), 
 operations teams and developers need to be able to offload a significant amount of operations and maintenance work. 
 These include tasks like provisioning infrastructure, 
 handling [service discovery](/service-discovery/) and load balancing, and [scaling](/scalability/) applications.

content/en/service-mesh.md

@@ -5,7 +5,7 @@ category: technology
 tags: ["networking", "", ""]
 ---
 
-In a [microservices](/microservices/) world, apps are broken down into multiple smaller [services](/service/) that communicate over a network. 
+In a [microservices](/microservices-architecture/) world, apps are broken down into multiple smaller [services](/service/) that communicate over a network. 
 Just like your wifi network, computer networks are intrinsically unreliable, hackable, and often slow. 
 Service meshes address this new set of challenges by managing traffic (i.e., communication) between services and 
 adding [reliability](/reliability/), [observability](/observability/), and security features uniformly across all services.

content/en/service.md

@@ -9,4 +9,4 @@ Please note that in IT, service has multiple meanings.
 In this definition, we'll focus on the more traditional one: service as in microservice. 
 How or even if services differ from microservices is nuanced and different people may have different opinions. 
 For a high-level definition, we'll treat them as the same. 
-Please refer to the [microservices](/microservices/) definition.
+Please refer to the [microservices](/microservices-architecture/) definition.

content/en/tightly-coupled-architecture.md

@@ -14,7 +14,7 @@ They also tend to require coordinated rollouts of components
 which can become a drag on developer productivity.
 
 Tightly coupled application architectures are a fairly traditional way of building applications. 
-While not necessarily consistent with all the best practices of [microservice](/microservices/) development 
+While not necessarily consistent with all the best practices of [microservice](/microservices-architecture/) development 
 they can be useful in specific circumstances. 
 They tend to be faster and simpler to implement and 
 much like [monolithic applications](/monolithic-apps/) they can speed up the initial development cycle.