[hi] added firewall in hindi

LOCALIZATION.md

@@ -134,3 +134,4 @@ To join an existing team, hop on the #glossary-localizations and #glossary-local
 
 If the team seems inactive (no response after several days), reach out to @Seokho Son, @Catherine Paganini, and @jmo on the #glossary-localizations channel.  
 
+Note, that every localization team may have their own process of working on localizing terms. However, one thing is common for all localization teams and important to keep in mind: Contributions have to be based on the `dev-xx` branch and PRs need to target `dev-xx`.

content/en/_index.md

@@ -19,7 +19,9 @@ Anyone who wishes to make a contribution may submit a GitHub issue or create a p
 The Cloud Native Glossary was initiated by the CNCF Marketing
 Committee (Business Value Subcommittee) and includes
 contributions from [Catherine Paganini](https://www.linkedin.com/in/catherinepaganini/en/), [Chris Aniszczyk](https://www.linkedin.com/in/caniszczyk/),
-[Daniel Jones](https://www.linkedin.com/in/danieljoneseb/?originalSubdomain=uk), [Jason Morgan](https://www.linkedin.com/in/jasonmorgan2/), [Katelin Ramer](https://www.linkedin.com/in/katelinramer/), [Mike Foster](https://www.linkedin.com/in/mfosterche/?originalSubdomain=ca), [Seokho Son](https://www.linkedin.com/in/seokho-son/) and many more contributors. For a complete contributor list, please refer to [this GitHub page](https://github.com/cncf/glossary/graphs/contributors).
+[Daniel Jones](https://www.linkedin.com/in/danieljoneseb/?originalSubdomain=uk), [Jason Morgan](https://www.linkedin.com/in/jasonmorgan2/), [Katelin Ramer](https://www.linkedin.com/in/katelinramer/), [Mike Foster](https://www.linkedin.com/in/mfosterche/?originalSubdomain=ca), and many more contributors. For a complete contributor list, please refer to [this GitHub page](https://github.com/cncf/glossary/graphs/contributors).
+
+The Glossary is maintained by [Catherine Paganini](https://www.linkedin.com/in/catherinepaganini/en/), [Jason Morgan](https://www.linkedin.com/in/jasonmorgan2/), [Jihoon Seo](https://www.linkedin.com/in/jihoon-seo/), [Noah Ispas](https://www.linkedin.com/in/noah-ispas-0665b42a/), and [Seokho Son](https://www.linkedin.com/in/seokho-son/).
 
 ## License
 

content/en/auto_scaling.md

@@ -10,4 +10,6 @@ Previously, infrastructure and applications were architected to consider peak sy
 
 By leveraging the cloud, [virtualizing](/virtualization/), and [containerizing](/containerization/) applications and their dependencies, organizations can build applications that scale according to user demands. They can monitor application demand and automatically scale them, providing an optimal user experience. Take the increase in viewership Netflix experiences every Friday evening. Autoscaling out means dynamically adding more resources: for example, increasing the number of servers allowing for more video streaming and scaling back once consumption has normalized.
 
-
+## Please also refer to
+* [Horizontal Scaling](/horizontal_scaling/)
+* [Vertical Scaling](/vertical_scaling/)

content/en/continuous_delivery.md

@@ -13,4 +13,8 @@ Deploying [reliable](/reliability/) updates becomes a problem at scale. Ideally,
 ## How it helps
 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. Typically, trunk-based development is used in CD strategies as opposed to feature branching or pull requests.
 
+## Please also refer to
+* [Continuous Integration](/continuous_integration/)
+* [Continuous Deployment](/continuous_deployment/)
+
 

content/en/continuous_deployment.md

@@ -15,3 +15,7 @@ Releasing new software versions can be a labor-intensive and error-prone process
 ## How it helps
 
 By automating the release cycle and forcing organizations to release to production more frequently, CD does what CI did for development teams for operations teams. Specifically, it forces operations teams to automate the painful and error-prone portions of production deployments, reducing overall risk. It also makes organizations better at accepting and adapting to production changes, which leads to higher stability.
+
+## Please also refer to
+* [Continuous Integration](/continuous_integration/)
+* [Continuous Delivery](/continuous_delivery/)

content/en/continuous_integration.md

@@ -13,3 +13,6 @@ Software systems are often large and complex, with numerous developers maintaini
 ## How it helps
 CI software automatically checks that code changes merge cleanly whenever a developer commits a change. It's a near-ubiquitous practice to use the CI server to run code quality checks, tests, and even deployments. As such, it becomes a concrete implementation of quality control within teams. CI allows software teams to turn every code commit into either a concrete failure or a viable release candidate.
 
+## Please also refer to
+* [Continuous Delivery](/continuous_delivery/)
+* [Continuous Deployment](/continuous_deployment/)

content/en/contribute/_index.md

@@ -36,7 +36,7 @@ Additionally, please also join the [#glossary](https://cloud-native.slack.com/ar
 Once they assign it to you, you can start working on it. For the next steps, please refer to the [Submitting a new term (creating a PR)](#submitting-a-new-term-creating-a-pr) section.
 
 ## 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.
+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. Please note that terms must meet the [CNCF's cloud native definition](https://github.com/cncf/toc/blob/main/DEFINITION.md). The only exceptions are foundational terms needed to understand cloud native concepts.
 
 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! 
 
@@ -83,7 +83,7 @@ Copy the content…
 
 ![create new file](/images/how-to/howto-09.png)
 
-Add the term name in the URL (no capitalization and no space) and .md at the end (note: if your preview doesn't work, you probably forgot to add .md at the end). Now paste the template content below. Copy and paste your definition into the file. Note that GitHub uses markdown to format the text (e.g., hyperlink, bold, italic). Please refer to this [markdown cheat sheet](https://www.markdownguide.org/cheat-sheet/). To verify you've used markdown as intended, go to "preview."
+Add the term name in the URL (no capitalization and no space) and .md at the end (note: if your preview doesn't work, you probably forgot to add .md at the end). Now paste the template content below. Copy and paste your definition into the file. To make reviews easier, please **use [semantic line breaks](https://sembr.org/)** (e.g. one line per sentence). Note that GitHub uses markdown to format the text (e.g., hyperlink, bold, italic). Please refer to this [markdown cheat sheet](https://www.markdownguide.org/cheat-sheet/). To verify you've used markdown as intended, go to "preview."
 
 ![finalize term](/images/how-to/howto-10.png)
 

content/en/horizontal_scaling.md

@@ -17,3 +17,7 @@ As demand for an application grows beyond the current capacity of that applicati
 ## How it helps
 
 Horizontal scaling allows applications to scale to whatever limits the underlying cluster provides. By adding more instances to the system, the app can process a greater number of requests. If a single node can handle 1,000 requests per second, each additional node should increase the total number of requests by around 1,000 requests per second. This allows the application to do more work concurrently without needing to increase the capacity of any node in particular.
+
+## Please also refer to
+* [Vertical Scaling](/vertical_scaling/)
+* [Auto Scaling](/auto_scaling/)

content/en/style-guide/_index.md

@@ -23,7 +23,7 @@ The Cloud Native Glossary follows the [default style guide](https://github.com/c
 
 ## Audience
 
-The Glossary is written for a technical AND non-technical audience. Please ensure definitions are explained in simple terms and don’t assume technical knowledge. More do that below under Definition.
+The Glossary is written for a technical AND non-technical audience. Please ensure definitions are explained in simple terms and don’t assume technical knowledge. More do that below under Definition. 
 
 ## Definition Template
 
@@ -104,6 +104,8 @@ The definitions for **technology** and **concept** categories contain three subh
 
 Note that **properties** don't require separate sections. A definition will suffice. 
 
+To facilitate review, please use **semantic line breaks** (one sentence per line).
+
 #### Quality is paramount
 
 If merged, your submission will be the official CNCF definition for that term (until someone else improves it). Creating a term that meets the CNCF's high standards can't be rushed — quality takes time and effort.
@@ -112,6 +114,8 @@ If merged, your submission will be the official CNCF definition for that term (u
 
 **Don't plagiarize**. The same rules apply to Glossary as to any other serious publication. Don't copy and paste other people's work unless you are quoting and contributing it to them. If you like a particular section of a definition, paraphrase it in your own words.
 
+**Reference authoritative resources**. When possible, link to authoritative resources such as project docs. Note that we cannot link to content developed by vendors. 
+
 #### Keeping it simple
 
 The Glossary aims at **explaining complex concepts in simple words** — that is a surprisingly difficult task that will likely take multiple revisions. Always keep the audience in mind when drafting your definition. Avoid using industry terms and buzzwords — you'll probably catch yourself going back to them and may need to autocorrect. 

content/en/vertical_scaling.md

@@ -15,3 +15,7 @@ As demand for an application grows beyond the current capacity of that applicati
 ## How it helps
 
 Vertical scaling allows you to resize your server without changing the application code. That contrasts to horizontal scaling, where the app must be replicable to scale, potentially requiring code updates. Vertical scaling increases the capacity of an existing application by adding compute resources, allowing the app to process more requests and do more work concurrently.
+
+## Please also refer to
+* [Horizontal Scaling](/horizontal_scaling/)
+* [Auto Scaling](/auto_scaling/)

content/hi/firewall.md

@@ -0,0 +1,15 @@
+---
+title: फ़ायरवॉल (Firewall)
+status: Completed
+category: प्रौद्योगिकी
+exclude_search: true
+---
+
+### यह क्या है
+फ़ायरवॉल (Firewall) एक सिस्टम है जो निर्दिष्ट नियमों के आधार पर नेटवर्क ट्रैफ़िक को छानकर शुद्ध करता है। फायरवॉल हार्डवेयर, सॉफ्टवेयर या दोनों का संयोजन हो सकता है।
+
+### समस्या 
+डिफ़ॉल्ट रूप से, जब तक वे नेटवर्क के रूटिंग नियमों का पालन करते हैं, नेटवर्क किसी को भी प्रवेश करने और प्रस्थान करने की अनुमति देगा। इस डिफ़ॉल्ट व्यवहार के कारण, नेटवर्क को सुरक्षित करना चुनौतीपूर्ण है। उदाहरण के लिए, एक माइक्रोसर्विस-आधारित बैंकिंग ऐप में, सेवाएं अपने नेटवर्क के माध्यम से अत्यधिक संवेदनशील वित्तीय डेटा संचारित करके एक दूसरे के साथ संचार करती हैं। एक दुर्भावनापूर्ण अभिनेता नेटवर्क में घुसपैठ कर सकता है, संचार को बाधित कर सकता है, और अगर जगह में कोई फ़ायरवॉल नहीं है तो नुकसान कर सकता है।
+
+### समाधान 
+फ़ायरवॉल पूर्व-निर्धारित नियमों का उपयोग करके नेटवर्क ट्रैफ़िक की जाँच करता है। सभी ट्रैफ़िक को फ़िल्टर के उपयोग से छानकर शुद्ध किया जाता है, और अविश्वसनीय या संदिग्ध स्रोतों से आने वाले किसी भी ट्रैफ़िक को अवरुद्ध कर दिया जाता है - केवल स्वीकार किए जाने के लिए कॉन्फ़िगर किया गया ट्रैफ़िक ही अंदर आता है। फ़ायरवॉल सुरक्षित और नियंत्रित आंतरिक विश्वसनीय नेटवर्क के बीच एक अवरोध स्थापित करते हैं।

wordlist.txt

@@ -196,3 +196,6 @@ yaml
 yml
 DBaaS
 DBA
+Ispas
+Jihoon
+Seo