Merge pull request #2993 from cncf/main

[ja] Merge `main` into `dev-ja` to sync-up

Author: seokho-son

CODEOWNERS

@@ -75,5 +75,5 @@
 /i18n/zh-cn.toml @hanyuancheung @Jacob953 @Rocksnake @Submarinee
 
 # Approvers for Traditional Chinese contents
-/content/zh-tw/ @pichuang @ydFu @hwchiu @johnlinp
-/i18n/zh-tw.toml @pichuang @ydFu @hwchiu @johnlinp
+/content/zh-tw/ @tico88612 @ydFu @hwchiu @johnlinp
+/i18n/zh-tw.toml @tico88612 @ydFu @hwchiu @johnlinp

LOCALIZATION.md

@@ -57,26 +57,31 @@ Open a PR with the localization initiation following this example: https://githu
 
 To add a new language to the site, modify [config.toml](https://github.com/cncf/glossary/blob/main/config.toml#L54) (Note: localization teams should use their assigned development branch for this).
 
-The `[languages]` block of `config.toml` is used to set the language. For instance, `[languages.en]` stands for English and `[languages.ko]` for Korean language configuration. Go to the `[languages]` block in `config.toml` and add a new block for your language-specific configuration. For instance, the Korean localization team added its `[languages.ko]` block after the `[languages.en]` block.
+The `[languages]` block of `config.toml` is used to set the language. For instance, `[languages.en]` stands for English and `[languages.ko]` for Korean language configuration. Go to the `[languages]` block in `config.toml` and find a place for your new localization:
+
+ - The English language always stays first.
+ - Other languages are sorted based on the alphabetized English translation of their names (see how currently existing localizations are ordered as an example).
+ - Each localization is written in its own language followed by the English translation in parentheses — e.g., `한국어 (Korean)`.
+ - The `weight` parameter in the config is used for sorting (`1` is for English, `2` is for the alphabetically first language, `3` is for the second one, and so on).
+
+For instance, you're adding a new block for the Korean localization. You calculated its weight as 8. Find the language block with `weight = 7` and add your new block afterwards:
 
 - Example of `New language block for /config.toml`
   ```diff
   [languages]
-  [languages.en]
-  title = "Cloud Native Glossary"
-  description = "The CNCF Cloud Native Glossary Project is intended to be used as a reference for common terms used when talking about cloud native applications."
-  languageName ="English"
-  # Weight used for sorting.
-  weight = 1
+  ...
+  weight = 7
 
   +[languages.ko]
   +title = "클라우드 네이티브(Cloud Native) 용어집"
   +description = "CNCF 클라우드 네이티브 용어집 프로젝트는 클라우드 네이티브 애플리케이션에 대한 대화를 나눌 때 공통의 용어를 참조하여 사용하도록 하는 목적을 가지고 있다."
-  +languageName ="한국어(Korean)"
+  +languageName = "한국어 (Korean)"
   +contentDir = "content/ko"
-  +weight = 2
+  +weight = 8
   ```
 
+Since the `weight` values should always be kept consistent, please **remember to increment the weights** of all the languages following your newly added localization.
+
 #### 3-2. Adding a file for site strings
 
 `i18n/<localization>.toml` sets up language-specific site strings.

config.toml

@@ -68,85 +68,85 @@ description = "The CNCF Cloud Native Glossary Project is intended to be used as
 #time_format_default = "02.01.2006"
 #time_format_blog = "02.01.2006"
 
+[languages.bn]
+contentDir = "content/bn"
+languageName = "বাংলা (Bengali)"
+title = "ক্লাউড নেটিভ শব্দকোষ"
+weight = 2
+[languages.bn.params]
+description = "CNCF ক্লাউড নেটিভ শব্দকোষ প্রকল্পটি ক্লাউড নেটিভ অ্যাপ্লিকেশন সম্পর্কে কথা বলার সময় ব্যবহৃত সাধারণ পদগুলির জন্য একটি রেফারেন্স হিসাবে ব্যবহার করার উদ্দেশ্যে।"
+
+[languages.fr]
+contentDir = "content/fr"
+languageName = "Français (French)"
+title = "Glossaire Cloud Native"
+weight = 3
+[languages.fr.params]
+description = "Le projet de Glossaire CNCF Cloud Native a pour objectif de référencer les termes courants utilisés dans les différentes applications Cloud Natives."
+
+[languages.de]
+contentDir = "content/de"
+languageName = "Deutsch (German)"
+title = "Cloud Native Glossar"
+weight = 4
+[languages.de.params]
+description = "Das CNCF Cloud Native Glossar soll als Referenz für gängige Begriffe dienen, die im Zusammenhang mit Cloud Native Anwendungen verwendet werden."
+
 [languages.hi]
 contentDir = "content/hi"
 languageName = "हिन्दी (Hindi)"
 title = "क्लाउड नेटिव शब्दावली"
-weight = 2
+weight = 5
 [languages.hi.params]
 description = "CNCF क्लाउड नेटिव शब्दावली परियोजना का उद्देश्य क्लाउड नेटिव एप्लिकेशन के बारे में बात करते समय प्रयोग किए जाने वाले सामान्य शब्दों के संदर्भ के रूप में उपयोग किया जाना है।"
 
-[languages.pt-br]
-contentDir = "content/pt-br"
-languageName = "Português"
-title = "Glossário Cloud Native"
-weight = 3
-[languages.pt-br.params]
-description = "O Projeto CNCF Glossário Cloud Native se destina a ser usado como uma referência para termos comuns usados ao falar sobre aplicações nativas de nuvem."
-
 [languages.it]
 contentDir = "content/it"
-languageName = "Italiano"
+languageName = "Italiano (Italian)"
 title = "Glossario Cloud Native"
-weight = 4
+weight = 6
 [languages.it.params]
 description = "Il progetto del Glossario CNCF Cloud Native è pensato per essere un riferimento per i termini comuni, usati nell'ambito delle applicazioni cloud native."
 
+[languages.ja]
+contentDir = "content/ja"
+languageName = "日本語 (Japanese)"
+title = "クラウドネイティブ用語集"
+weight = 7
+[languages.ja.params]
+description = "CNCF クラウドネイティブ用語集プロジェクトは、クラウドネイティブアプリケーションについて話すときに使われる一般的な用語のリファレンスとして使用することを目的としています。"
+
 [languages.ko]
 contentDir = "content/ko"
 languageName = "한국어 (Korean)"
 title = "클라우드 네이티브(Cloud Native) 용어집"
-weight = 5
+weight = 8
 [languages.ko.params]
 description = "CNCF 클라우드 네이티브 용어집 프로젝트는 클라우드 네이티브 애플리케이션을 주제로 대화를 나눌 때 참조할 수 있는 공통의 용어 제공을 목표로 한다."
 
-[languages.es]
-contentDir = "content/es"
-languageName = "Español (Spanish)"
-title = "Cloud Native Glosario"
-weight = 6
-[languages.es.params]
-description = "El proyecto de CNCF Cloud Native Glosario pretende ser usado como una referencia para los terminos comunes usados cuando se habla acerca de las aplicaciones nativas para la nube."
+[languages.pt-br]
+contentDir = "content/pt-br"
+languageName = "Português (Portuguese)"
+title = "Glossário Cloud Native"
+weight = 9
+[languages.pt-br.params]
+description = "O Projeto CNCF Glossário Cloud Native se destina a ser usado como uma referência para termos comuns usados ao falar sobre aplicações nativas de nuvem."
 
 [languages.zh-cn]
 contentDir = "content/zh-cn"
 languageName = "简体中文 (Simplified Chinese)"
 title = "Cloud Native(云原生) Glossary"
-weight = 7
+weight = 10
 [languages.zh-cn.params]
 description = "CNCF 云原生 Glossary 项目旨在用作讨论云原生应用程序时常用术语的参考"
 
-[languages.bn]
-contentDir = "content/bn"
-languageName = "বাংলা (Bengali)"
-title = "ক্লাউড নেটিভ শব্দকোষ"
-weight = 8
-[languages.bn.params]
-description = "CNCF ক্লাউড নেটিভ শব্দকোষ প্রকল্পটি ক্লাউড নেটিভ অ্যাপ্লিকেশন সম্পর্কে কথা বলার সময় ব্যবহৃত সাধারণ পদগুলির জন্য একটি রেফারেন্স হিসাবে ব্যবহার করার উদ্দেশ্যে।"
-
-[languages.de]
-contentDir = "content/de"
-languageName = "Deutsch"
-title = "Cloud Native Glossar"
-weight = 9
-[languages.de.params]
-description = "Das CNCF Cloud Native Glossar soll als Referenz für gängige Begriffe dienen, die im Zusammenhang mit Cloud Native Anwendungen verwendet werden."
-
-[languages.ur]
-contentDir = "content/ur"
-languageName = "اردو (Urdu)"
-title = "کلاؤڈ کی مقامی لغت"
-weight = 10
-[languages.ur.params]
-description = "CNCF کلاؤڈ کی مقامی لغت کا مقصد کلاؤڈ مقامی ایپلی کیشنز کے بارے میں بات کرتے وقت استعمال ہونے والی عام اصطلاحات کے حوالے کے طور پر استعمال کرنا ہے۔"
-
-[languages.fr]
-contentDir = "content/fr"
-languageName = "Français (French)"
-title = "Glossaire Cloud Native"
+[languages.es]
+contentDir = "content/es"
+languageName = "Español (Spanish)"
+title = "Cloud Native Glosario"
 weight = 11
-[languages.fr.params]
-description = "Le projet de Glossaire CNCF Cloud Native a pour objectif de référencer les termes courants utilisés dans les différentes applications Cloud Natives."
+[languages.es.params]
+description = "El proyecto de CNCF Cloud Native Glosario pretende ser usado como una referencia para los terminos comunes usados cuando se habla acerca de las aplicaciones nativas para la nube."
 
 [languages.zh-tw]
 contentDir = "content/zh-tw"
@@ -156,21 +156,21 @@ weight = 12
 [languages.zh-tw.params]
 description = "CNCF 雲端原生 Glossary 專案旨在用作討論雲端原生應用程式時常用術語的參考"
 
-[languages.ja]
-contentDir = "content/ja"
-languageName = "日本語 (Japanese)"
-title = "クラウドネイティブ用語集"
-weight = 13
-[languages.ja.params]
-description = "CNCF クラウドネイティブ用語集プロジェクトは、クラウドネイティブアプリケーションについて話すときに使われる一般的な用語のリファレンスとして使用することを目的としています。"
-
 [languages.tr]
 title = "Cloud Native Sözlüğü"
-description = "CNCF Cloud Native Sözlüğü projesi, cloud native uygulamalardan bahsederken kullanılan yaygın terimler için bir referans olarak kullanılmak üzere tasarlanmıştır."
 languageName ="Türkçe (Turkish)"
 contentDir = "content/tr"
-# Weight used for sorting.
+weight = 13
+[languages.tr.params]
+description = "CNCF Cloud Native Sözlüğü projesi, cloud native uygulamalardan bahsederken kullanılan yaygın terimler için bir referans olarak kullanılmak üzere tasarlanmıştır."
+
+[languages.ur]
+contentDir = "content/ur"
+languageName = "اردو (Urdu)"
+title = "کلاؤڈ کی مقامی لغت"
 weight = 14
+[languages.ur.params]
+description = "CNCF کلاؤڈ کی مقامی لغت کا مقصد کلاؤڈ مقامی ایپلی کیشنز کے بارے میں بات کرتے وقت استعمال ہونے والی عام اصطلاحات کے حوالے کے طور پر استعمال کرنا ہے۔"
 
 [markup]
 [markup.goldmark]

content/en/container-orchestration.md

@@ -4,7 +4,7 @@ status: Completed
 category: Concept
 ---
 
-[Container](/container/) orchestration refers to managing and automating the lifecycle of containerized applications in dynamic environments. 
+[Container](/container/) orchestration refers to managing and automating the lifecycle of [containerized](/containerization/) applications in dynamic environments. 
 It's executed through a container orchestrator (in most cases, [Kubernetes](/kubernetes)), which enables deployments, (auto)scaling, auto-healing, and monitoring. 
 Orchestration is a metaphor:
 The orchestration tool conducts containers like a music conductor, ensuring every container (or musician) does what it should. 

content/en/containerization.md

@@ -11,7 +11,7 @@ As long as the output is a container image that adheres to this standard, which
 
 ## Problem it addresses 
 
-Before containers became prevalent, organizations relied on virtual machines (VMs) to 
+Before [containers](/container/) became prevalent, organizations relied on [virtual machines](/virtual-machine/) (VMs) to 
 orchestrate multiple applications on a single [bare-metal machine](/bare-metal-machine/). 
 VMs are significantly larger than containers and require a hypervisor to run. 
 Due to the storage, backup, and transfer of these larger VM templates, creating the VM templates is also slow. 

content/en/continuous-delivery.md

@@ -10,8 +10,9 @@ in which code changes are automatically deployed into an acceptance environment
 (or, in the case of continuous deployment, into production). 
 CD crucially includes procedures to ensure that software is adequately tested 
 before deployment and provides a way to rollback changes if deemed necessary. 
-Continuous integration (CI) is the first step towards continuous delivery 
-(i.e., changes have to merge cleanly before being tested and deployed).
+[Continuous integration](/continuous-integration/) (CI) is the first step towards 
+continuous delivery (i.e., changes have to merge cleanly before being tested and 
+deployed).
 
 ## Problem it addresses
 
@@ -26,7 +27,7 @@ deploying more changes at once and increasing the risk that something goes wrong
 CD strategies create a fully automated path to production 
 that tests and deploys the software using various deployment strategies 
 such as [canary](/canary-deployment/) or [blue-green](/blue-green-deployment/) releases. 
-This allows developers to deploy code frequently,  giving them peace of mind that the new revision has been tested. 
+This allows developers to deploy code frequently, giving them peace of mind that the new revision has been tested. 
 
 ## Related terms
 

content/en/edge-computing.md

@@ -4,7 +4,7 @@ status: Completed
 category: Technology
 ---
 
-Edge computing is a [distributed system](/distributed-systems/) approach that shifts some storage and computing capacity from the primary data center to the data source.
+Edge computing is a [distributed system](/distributed-systems/) approach that shifts some storage and computing capacity from the primary [data center](/data-center/) to the data source.
 The gathered data is computed locally (e.g., on a factory floor, in a store, or throughout a city) rather than sent to a centralized data center for processing and analysis. 
 These local processing units or devices represent the system's edge, whereas the data center is its center.
 The output computed at the edge is then sent back to the primary data center for further processing.

content/en/ingress.md

@@ -15,14 +15,14 @@ The ingress controller is the web server technology that actually performs the r
 Cloud Native web applications consist of multiple services, and often, those [services](/service/) need to be accessible over the internet for users to visit using their browser.
 To make these services user accessible while using [Kubernetes](/kubernetes/) to run this application, we need to expose each application service to the outside world.
 The most straightforward way would be to use a Kubernetes Load Balancer Service.
-Creating such a Kubernetes Load Balancer Service results in a new component on the underlying infrastructure.
+But creating such a service results in a new component on the underlying infrastructure.
 This not only introduces new costs and management overhead, but each newly created Load Balancer has its own external IP address.
 This leads to a bad user experience, because as a user, we don’t want to browse different URLs to access an application.
 
 ## How it helps
 
 An Ingress resource allows you to configure how traffic is balanced and routed to an application’s services.
-The ingress controller is a web server that allows for a single entry point through a URL (www.example-url.com) and does the actual routing and balancing based on different URL paths (www.example-url.com/path).
+The ingress controller exposes a single entry point through a URL (www.example-url.com) and does the actual routing and balancing based on different URL paths (www.example-url.com/path).
 An Ingress controller is a component that runs within the cluster and interprets the rules defined in the Ingress resource.
 It is up to the cluster operators where the web app runs to choose a specific Ingress controller from a set of possible technologies like Nginx, Traefik, HAProxy, etc.
 So now, if an application consists of multiple services, the user can access it using a single URL.

content/en/virtual-machine.md

@@ -31,4 +31,4 @@ VMs allow you to use your existing physical hardware resources better
 by placing multiple virtual machines on a single physical machine. 
 Not bound to a particular physical machine, VMs are also more resilient than physical machines. 
 When a physical machine needs to go offline, 
-the VMs running on it can be moved to another machine with little to no downtime
+the VMs running on it can be moved to another machine with little to no downtime.

content/es/.wordlist.txt

@@ -235,6 +235,7 @@ PRs
 pull
 Quiceno
 Ramer
+RBAC
 RDS
 relevantes
 Reliability