[pt-br] Update dev-pt with the main branch

.github/workflows/es-spellcheck.yml

@@ -29,6 +29,6 @@ jobs:
           set -o errexit
           diff content/es/.wordlist.txt <(LC_ALL= sort -f content/es/.wordlist.txt)
       - name: GitHub Spellcheck Action
-        uses: rojopolis/spellcheck-github-actions@0.41.0
+        uses: rojopolis/spellcheck-github-actions@0.42.0
         with:
           config_path: content/es/.spellcheck.yml

.github/workflows/spellcheck.yml

@@ -25,4 +25,4 @@ jobs:
       - uses: actions/checkout@v4
 
       - name: GitHub Spellcheck Action
-        uses: rojopolis/spellcheck-github-actions@0.41.0
+        uses: rojopolis/spellcheck-github-actions@0.42.0

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

@@ -5,14 +5,14 @@ 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.
+Function as a Service (FaaS) is a [cloud computing](/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.
-Consequently, FaaS platforms can implement a true pay-as-you-go billing approach, eliminating costs when functions are dormant, distinguishing it from other models like [Platform as a Service (PaaS)](/platform-as-a-service/), which require continuous resource availability.
+This model supports an [autoscaling](/auto-scaling/) feature, enabling a function instance to be initiated per request and terminated post-execution, emphasizing its [stateless](/stateless-apps/) nature.
+Consequently, FaaS platforms can implement a true pay-as-you-go billing approach, eliminating costs when functions are dormant, distinguishing it from other models like Platform as a Service (PaaS), which require continuous resource availability.
 
 ## Problem it addresses
 
-Traditionally, businesses have relied on maintaining on-premises data centers, necessitating substantial investment in hardware, software, and personnel.
+Traditionally, businesses have relied on maintaining on-premises [data centers](/data-center/), necessitating substantial investment in hardware, software, and personnel.
 This setup demands resources to be scaled to peak demand, resulting in underutilized assets during downtime.
 Moreover, rapid business growth can overwhelm IT capabilities, leading to operational inefficiencies.
 In contrast, [Infrastructure-as-a-Service (IaaS)](/infrastructure-as-a-service/) models, while offering cloud-based solutions, still place the onus of scaling resources on the user, requiring payment for continuous server availability irrespective of actual usage.
@@ -23,6 +23,6 @@ FaaS gives developers an [abstraction](/abstraction/) for running web applicatio
 For example, an action such as uploading a file could trigger custom code that transcodes the file into various formats.
 The FaaS infrastructure automatically adjusts resources to match demand, freeing developers from the complexities of coding for [scalability](/scalability/).
 Charges apply solely for the duration of computation, ensuring no costs accrue when functions are inactive.
-	
+
 For more information, refer to the [Serverless](/serverless/) glossary entry.
-Although "serverless" and "FaaS" are often used as interchangeable terms, they embody distinct concepts.
+Although "serverless" and "FaaS" are often used as interchangeable terms, they embody distinct concepts.

content/en/horizontal-scaling.md

@@ -7,10 +7,11 @@ tags: ["infrastructure", "", ""]
 
 Horizontal scaling is a technique where a system's capacity is increased by adding more [nodes](/nodes/) 
 versus adding more compute resources to individual nodes (the latter being known as [vertical scaling](/vertical-scaling/)). 
-Let's say, we have a system of 4GB RAM and want to increase its capacity to 16GB RAM, 
-scaling it horizontally means doing so by adding 4 x 4GB RAM rather than switching to a 16GB RAM system.
+Let's say, we have a system of 4GB RAM and want to increase its capacity to 16GB RAM. 
+Scaling it horizontally means doing so by adding 3 nodes x 4GB RAM rather than switching to 
+a 16GB RAM system.
 
-This approach enhances the performance of an application by adding new instances, or [nodes](/nodes/), 
+This approach enhances the performance of an application by adding new instances, or nodes, 
 to better distribute the workload. 
 In simple words, it aims to decrease the server's load 
 rather than expanding capacity of the individual server.

content/en/serverless.md

@@ -9,12 +9,12 @@ tags: ["architecture", "", ""]
 Serverless Computing [abstracts](/abstraction/) servers away from the user.
 Operational management falls to the service provider, including handling physical machines and VM provisioning.
 Service providers can be public cloud entities or internal IT departments serving their development teams.
-These providers offer user interfaces such as SDKs, CLIs, or OCI-compliant runtimes, focusing on code and deployment tasks.
+These providers offer user interfaces such as SDKs, CLIs, or OCI-compliant [runtimes](/runtime/), focusing on code and deployment tasks.
 Charges are based on a pay-per-use model.
 [Scaling](/scalability/) and resource provisioning for computing, storage, or networking are automatically adjusted based on application demand without user intervention.
 A serverless platform provider consolidates resources to serve multiple users on a single physical machine, ensuring isolation through virtualization, especially with [VMs](/virtual-machine/).
 
-Serverless is a comprehensive term encompassing services with these attributes, extending from [Platform-as-a-Service (PaaS)](/platform-as-a-service/) to [Software-as-a-Service (SaaS)](/software-as-a-service/).
+Serverless is a comprehensive term encompassing services with these attributes, extending from Platform-as-a-Service (PaaS) to Software-as-a-Service (SaaS).
 
 ## Problem it addresses
 

content/en/stateless-apps.md

@@ -5,11 +5,10 @@
  tags: ["fundamental", "application", "property"]
 ---
 
-Stateless applications process requests as if each request were the first it's ever been sent. 
-The app doesn't "remember" previous interactions or user session data. 
-Data from previous interactions is referred to as state, and since that data isn't stored anywhere, these apps are state*less*. 
+Stateless applications handle each request independently without remembering any previous interactions or user data.
+Data from previous interactions is referred to as state since that data isn’t stored anywhere, these apps are state*less*. 
 Here's an example: 
 When you use a search engine, and that search is interrupted (e.g., the window is closed), those search results are lost. 
 You'll need to start all over.
 
-On the other hand, applications that process requests while considering previous interactions are called [stateful applications](/stateful-apps/). 
+On the other hand, applications that process requests while considering previous interactions are called [stateful applications](/stateful-apps/). 

content/hi/devops.md

@@ -10,7 +10,7 @@ DevOps एक कार्यप्रणाली है जिसमें ट
 
 ## समस्या
 
-परंपरागत रूप से, [टाइटली-कपल्ड](/tightly-coupled-architectures/) [मोनोलिथिक ऐप्स](/monolithic-apps/) का प्रयोग वाले जटिल संगठनों में, काम आम तौर पर कई समूहों के बीच खंडित होता था। इसमें एप्लीकेशन कई टीमों के बीच जाता था और काफी लम्बा समय लगता था। हर बार जब कोई घटक या अपडेट तैयार होता था, तो उसे अगली टीम के लिए एक कतार में रखा जाता था। क्योंकि प्रत्येक व्यक्ति केवल परियोजना के एक छोटे से हिस्से पर काम करता था, इस दृष्टिकोण के कारण स्वामित्व की कमी होती थी। उनका लक्ष्य काम को अगले समूह तक पहुंचाना था, न कि ग्राहक को सही कार्यक्षमता प्रदान करना - प्राथमिकताओं का एक स्पष्ट गलत संरेखण।
+परंपरागत रूप से, [टाइटली-कपल्ड](/tightly-coupled-architecture/) [मोनोलिथिक ऐप्स](/monolithic-apps/) का प्रयोग वाले जटिल संगठनों में, काम आम तौर पर कई समूहों के बीच खंडित होता था। इसमें एप्लीकेशन कई टीमों के बीच जाता था और काफी लम्बा समय लगता था। हर बार जब कोई घटक या अपडेट तैयार होता था, तो उसे अगली टीम के लिए एक कतार में रखा जाता था। क्योंकि प्रत्येक व्यक्ति केवल परियोजना के एक छोटे से हिस्से पर काम करता था, इस दृष्टिकोण के कारण स्वामित्व की कमी होती थी। उनका लक्ष्य काम को अगले समूह तक पहुंचाना था, न कि ग्राहक को सही कार्यक्षमता प्रदान करना - प्राथमिकताओं का एक स्पष्ट गलत संरेखण।
 
 जब तक कोड अंततः उत्पादन में आया, तब तक यह इतने सारे डेवलपर्स के माध्यम से चला गया, इतनी कतारों में प्रतीक्षा कर रहा था कि यदि कोड काम नहीं करता है तो समस्या की उत्पत्ति का पता लगाना मुश्किल था। DevOps ने इस दृष्टिकोण को पलट कर रख दिया।
 

layouts/partials/head.html

@@ -30,6 +30,7 @@
 {{- template "_internal/twitter_cards.html" . -}}
 
 <script src="https://cmp.osano.com/16A0DbT9yDNIaQkvZ/c3494b1e-ff3a-436f-978d-842e9a0bed27/osano.js"></script>
+<script defer src="https://www.cncf.io/wp-content/themes/cncf-twenty-two/source/js/on-demand/hello-bar-embed.js"></script>
 
 {{ partialCached "head-css.html" . "asdf" }}
 <script
@@ -49,11 +50,7 @@
 {{ partial "hooks/head-end.html" . }}
 <!--To comply with GDPR, cookie consent scripts places in head-end must execute before Google Analytics is enabled -->
 {{ if hugo.IsProduction }}
-  {{ if hasPrefix .Site.GoogleAnalytics "G-"}}
-    {{ template "_internal/google_analytics.html" . }}
-  {{ else }}
-    {{ template "_internal/google_analytics_async.html" . }}
-  {{ end }}
+  {{ template "_internal/google_analytics.html" . }}
 
   <!-- Google Tag Manager -->
   <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':

package.json

@@ -25,16 +25,14 @@
     "test": "npm run check:links",
     "update:pkgs": "npx npm-check-updates -u"
   },
-  "dependencies": {
-    "lunr-languages": "^1.9.0"
-  },
   "devDependencies": {
-    "autoprefixer": "^9.8.6",
-    "hugo-extended": "^0.115.2",
-    "postcss-cli": "^7.1.2"
+    "autoprefixer": "^10.4.19",
+    "hugo-extended": "^0.122.0",
+    "postcss": "^8.4.38",
+    "postcss-cli": "^11.0.0"
   },
   "optionalDependencies": {
-    "netlify-cli": "^17.26.1",
+    "netlify-cli": "^17.30.0",
     "npm-check-updates": "^16.14.20"
   },
   "enginesComment": "Ensure that engines.node value stays consistent with the project's .nvmrc",