From e0308f689450160a57b433c9a9ed85d368f63e52 Mon Sep 17 00:00:00 2001
From: bglglzd <bglglzd@gmail.com>
Date: Sun, 12 Jul 2026 21:16:47 +0300
Subject: [PATCH] Polish docs and comments in opensource.guide

---
 ...ibility-best-practices-for-your-project.md |  6 ++---
 _articles/ar/getting-paid.md                  |  2 +-
 _articles/ar/how-to-contribute.md             |  6 ++---
 ...ecurity-best-practices-for-your-project.md |  6 ++---
 ...ecurity-best-practices-for-your-project.md | 26 +++++++++----------
 docs/content-model.md                         |  2 +-
 6 files changed, 24 insertions(+), 24 deletions(-)

diff --git a/_articles/accessibility-best-practices-for-your-project.md b/_articles/accessibility-best-practices-for-your-project.md
index 4b9e7a00de4..a281af40895 100644
--- a/_articles/accessibility-best-practices-for-your-project.md
+++ b/_articles/accessibility-best-practices-for-your-project.md
@@ -210,7 +210,7 @@ Accessibility is easier to maintain when it's part of your regular process.
 
 Refer to this [accessibility issue template example](https://github.com/open-source-accessibility/accessibility-toolkit/blob/main/.github/ISSUE_TEMPLATE/accessibility.yml).
 
-### Add an accessibility checklist to pull requests (PRs) 
+### Add an accessibility checklist to pull requests (PRs)
 
 For projects with UI changes, include questions such as:
 
@@ -289,9 +289,9 @@ Refer to this [project for additional examples](https://github.com/mgifford/ACCE
 
 ## Conclusion: A few steps for you, a huge improvement for your users
 
-These steps might seem basic, but they go a long way to make your project more accessible. Every fix you make, whether it's a missing label, a keyboard trap, or a caption on a video, opens the door for someone who couldn't use your project before. 
+These steps might seem basic, but they go a long way to make your project more accessible. Every fix you make, whether it's a missing label, a keyboard trap, or a caption on a video, opens the door for someone who couldn't use your project before.
 
-Accessibility isn't a one-time fix, it's an ongoing practice, and you don't have to do it all at once. Start with keyboard navigation and semantics, keep changes small, and ask for review early. 
+Accessibility isn't a one-time fix, it's an ongoing practice, and you don't have to do it all at once. Start with keyboard navigation and semantics, keep changes small, and ask for review early.
 
 The work you put in today means more people can learn from, contribute to, and rely on what you build. That's a win worth celebrating.
 
diff --git a/_articles/ar/getting-paid.md b/_articles/ar/getting-paid.md
index 2198709006d..9bd6cfbe668 100644
--- a/_articles/ar/getting-paid.md
+++ b/_articles/ar/getting-paid.md
@@ -168,7 +168,7 @@ related:
 
 <aside markdown="1" class="pquote">
   <img src="https://avatars.githubusercontent.com/davegandy?s=180" class="pquote-avatar" alt="avatar">
-لسنوات عديدة، كنا المورد الرائد للأيقونات الملائمة للمواقع الإلكترونية، مع مجتمع يضم أكثر من 20 مليون شخص، وظهرنا في أكثر من 70 مليون موقع إلكتروني، بما في ذلك Whitehouse.gov. (...) صدرت النسخة 4 قبل ثلاث سنوات. تغيرت تقنية الويب كثيرًا منذ ذلك الحين، وبصراحة، أصبح Font Awesome قديمًا بعض الشيء. (...) لهذا السبب نقدم Font Awesome 5. نحن نقوم بتحديث وإعادة كتابة CSS وإعادة تصميم كل أيقونة من الألف إلى الياء. نحن نتحدث عن تصميم أفضل واتساق أفضل وقابلية قراءة أفضل. 
+لسنوات عديدة، كنا المورد الرائد للأيقونات الملائمة للمواقع الإلكترونية، مع مجتمع يضم أكثر من 20 مليون شخص، وظهرنا في أكثر من 70 مليون موقع إلكتروني، بما في ذلك Whitehouse.gov. (...) صدرت النسخة 4 قبل ثلاث سنوات. تغيرت تقنية الويب كثيرًا منذ ذلك الحين، وبصراحة، أصبح Font Awesome قديمًا بعض الشيء. (...) لهذا السبب نقدم Font Awesome 5. نحن نقوم بتحديث وإعادة كتابة CSS وإعادة تصميم كل أيقونة من الألف إلى الياء. نحن نتحدث عن تصميم أفضل واتساق أفضل وقابلية قراءة أفضل.
   <p markdown="1" class="pquote-credit">
 — @davegandy, [فيديو Font Awesome على Kickstarter](https://www.kickstarter.com/projects/232193852/font-awesome-5)
   </p>
diff --git a/_articles/ar/how-to-contribute.md b/_articles/ar/how-to-contribute.md
index b4bcf059f69..13055f007fd 100644
--- a/_articles/ar/how-to-contribute.md
+++ b/_articles/ar/how-to-contribute.md
@@ -16,7 +16,7 @@ related:
 
 <aside markdown="1" class="pquote">
   <img src="https://avatars.githubusercontent.com/errietta?s=180" class="pquote-avatar" alt="avatar">
-العمل على <span dir="rtl">Freenode</span> ساعدني على اكتساب الكثير من المهارات التي استخدمتها لاحقًا في دراستي الجامعية وفي عملي الفعلي. أعتقد أن العمل على مشاريع مفتوحة المصدر يساعدني بقدر ما يساعد المشروع! 
+العمل على <span dir="rtl">Freenode</span> ساعدني على اكتساب الكثير من المهارات التي استخدمتها لاحقًا في دراستي الجامعية وفي عملي الفعلي. أعتقد أن العمل على مشاريع مفتوحة المصدر يساعدني بقدر ما يساعد المشروع!
 <p markdown="1" class="pquote-credit">
 — [@errietta](https://github.com/errietta), ["Why I love contributing to open source software"](https://web.archive.org/web/20251207070642/https://www.errietta.me/blog/open-source/)
   </p>
@@ -99,7 +99,7 @@ related:
 
 <aside markdown="1" class="pquote">
   <img src="https://avatars.githubusercontent.com/kittens?s=180" class="pquote-avatar" alt="avatar">
- بجديّة، [التوثيق] مهم جدًّا. حتى الآن، كان التوثيق ممتازًا وكان ميزة قوية في <span dir="rtl">Babel</span>. هناك أقسام بالتأكيد يمكن تحسينها، وحتى إضافة فقرة هنا أو هناك تُقدّر كثيرًا. 
+ بجديّة، [التوثيق] مهم جدًّا. حتى الآن، كان التوثيق ممتازًا وكان ميزة قوية في <span dir="rtl">Babel</span>. هناك أقسام بالتأكيد يمكن تحسينها، وحتى إضافة فقرة هنا أو هناك تُقدّر كثيرًا.
 <p markdown="1" class="pquote-credit">
 — @kittens, ["Call for contributors"](https://github.com/babel/babel/issues/1347)
   </p>
@@ -146,7 +146,7 @@ related:
 
 <aside markdown="1" class="pquote">
   <img src="https://avatars.githubusercontent.com/shaunagm?s=180" class="pquote-avatar" alt="avatar">
-إذا ذهبت إلى متتبع المشكلات<span dir="rtl">(issue tracker)</span> وبدا الأمر محيرًا، فأنت لست وحدك. هذه الأدوات تتطلب الكثير من المعرفة الضمنية، لكن يمكن للناس مساعدتك في التنقل خلالها ويمكنك طرح الأسئلة عليهم.  
+إذا ذهبت إلى متتبع المشكلات<span dir="rtl">(issue tracker)</span> وبدا الأمر محيرًا، فأنت لست وحدك. هذه الأدوات تتطلب الكثير من المعرفة الضمنية، لكن يمكن للناس مساعدتك في التنقل خلالها ويمكنك طرح الأسئلة عليهم.
 <p markdown="1" class="pquote-credit">
 — @shaunagm, ["How to Contribute to Open Source"](https://readwrite.com/2014/10/10/open-source-diversity-how-to-contribute/)
   </p>
diff --git a/_articles/ar/security-best-practices-for-your-project.md b/_articles/ar/security-best-practices-for-your-project.md
index b0747e82348..90a03a56731 100644
--- a/_articles/ar/security-best-practices-for-your-project.md
+++ b/_articles/ar/security-best-practices-for-your-project.md
@@ -15,7 +15,7 @@ image: /assets/images/cards/security-best-practices.png
 
 ### ممثل  خبيث يتمكن من انتحال شخصية مساهم ذو امتيازات في مشروعك، سوف يتسبب في أضرار كارثية.
 
-بمجرد حصوله على حق الوصول المميز، يمكن لهذا الفاعل تعديل الكود الخاص بك لجعله يقوم بإجراءات غير مرغوب فيها (على سبيل المثال، تعدين العملة المشفرة),أو يمكنه نشر البرامج الضارة على البنية التحتية لمستخدميك،أو يمكنه الوصول إلى ملفات الكود علىGithub  لاستخراج الملكية الفكرية والبيانات الحساسة، بما في ذلك مفاتيح الوصول إلى خدمات أخرى. 
+بمجرد حصوله على حق الوصول المميز، يمكن لهذا الفاعل تعديل الكود الخاص بك لجعله يقوم بإجراءات غير مرغوب فيها (على سبيل المثال، تعدين العملة المشفرة),أو يمكنه نشر البرامج الضارة على البنية التحتية لمستخدميك،أو يمكنه الوصول إلى ملفات الكود علىGithub  لاستخراج الملكية الفكرية والبيانات الحساسة، بما في ذلك مفاتيح الوصول إلى خدمات أخرى.
 
 MFA توفر طبقة اضافية من الأمان ضد سؤقة الحساب. عندما تفعل يجب أن تسجل الدخول باسم مستخدمك وكلمة المرور بالاضافة الى شكل أخر من المصادقة أنت فقط تعرفه أو تستطيع الوصول إليه.
 
@@ -47,7 +47,7 @@ MFA توفر طبقة اضافية من الأمان ضد سؤقة الحساب.
 
 ### Dependencies في مشروعك ممكن أن تحتوي على ثغرات قد تخترقه. القيام بتحديث الDependencies يدويا باليد ستكون مهمة مستهلكة للوقت.
 
-تخيل هذا: مشروع مبني على أساس قوي لمكتبة مستخدمة على نطاق واسع , لاحقا المكتبة تواجه مشكلة أمنية كبيرة.لكن الناس الذين بنوا المشروع باستخدامها لا يعرفون عن هذه المشكلة. تُترك بيانات المستخدم الحساسة مكشوفة عندما يستغل المهاجم هذا الضعف، فينقض عليها للاستيلاء عليها. هذا ليس مثالا نظريا انما ما حدث تماما في  في 2017.لقد فشلوا في تحديث Apache Struts dependeny الخاص بهم بعد اشعارهم عن وجود ثغرة في الخادم.لقد تم استغلال هذه الثغرة، وأثرت عملية الاختراق الشهيرة لشركة Equifax على بيانات 144 مليون مستخدم.  
+تخيل هذا: مشروع مبني على أساس قوي لمكتبة مستخدمة على نطاق واسع , لاحقا المكتبة تواجه مشكلة أمنية كبيرة.لكن الناس الذين بنوا المشروع باستخدامها لا يعرفون عن هذه المشكلة. تُترك بيانات المستخدم الحساسة مكشوفة عندما يستغل المهاجم هذا الضعف، فينقض عليها للاستيلاء عليها. هذا ليس مثالا نظريا انما ما حدث تماما في  في 2017.لقد فشلوا في تحديث Apache Struts dependeny الخاص بهم بعد اشعارهم عن وجود ثغرة في الخادم.لقد تم استغلال هذه الثغرة، وأثرت عملية الاختراق الشهيرة لشركة Equifax على بيانات 144 مليون مستخدم.
 
 لمنع سيناريوهات كهذه, أدوات تحليل تكوين البرمجيات (SCA) مثل  Dependabot,Renvate تتحقق بشكل تلقائي من Dependencies الخاصة بك لأكثر الثغرات انتشارا في قواعد البيانات العامة مثل NVD,the Github Advisory Database ثم تنشأ pull requests لتحديثهم لأخر نسخ. مواكبة أخر التحديثات لل Dependencies الخاصة بمشروعك تحميه وتمنعه من المخاطر المحتملة.
 
@@ -82,6 +82,6 @@ MFA توفر طبقة اضافية من الأمان ضد سؤقة الحساب.
 تم كتابة هذا الدليل بواسطة [@nanzggits](https://github.com/nanzggits) & [@xcorail](https://github.com/xcorail) بمشاركة مساهمي من:
 
 [@JLLeitschuh](https://github.com/JLLeitschuh)
-[@intrigus-lgtm](https://github.com/intrigus-lgtm) + آخرون 
+[@intrigus-lgtm](https://github.com/intrigus-lgtm) + آخرون
 
 </div>
diff --git a/_articles/security-best-practices-for-your-project.md b/_articles/security-best-practices-for-your-project.md
index 62d7a3b35eb..1ad785cfa29 100644
--- a/_articles/security-best-practices-for-your-project.md
+++ b/_articles/security-best-practices-for-your-project.md
@@ -14,7 +14,7 @@ Bugs and new features aside, a project's longevity hinges not only on its useful
 
 ### A malicious actor who manages to impersonate a privileged contributor to your project will cause catastrophic damages.
 
-Once they obtain the privileged access, this actor can modify your code to make it perform unwanted actions (e.g. mine cryptocurrency), or can distribute malware to your users' infrastructure, or can access private code repositories to exfiltrate intellectual property and sensitive data, including credentials to other services. 
+Once they obtain the privileged access, this actor can modify your code to make it perform unwanted actions (e.g. mine cryptocurrency), or can distribute malware to your users' infrastructure, or can access private code repositories to exfiltrate intellectual property and sensitive data, including credentials to other services.
 
 MFA provides an additional layer of security against account takeover. Once enabled, you have to log in with your username and password and provide another form of authentication that only you know or have access to.
 
@@ -22,9 +22,9 @@ MFA provides an additional layer of security against account takeover. Once enab
 
 ### Security vulnerabilities in your code are cheaper to fix when detected early in the process than later, when they are used in production.
 
-Use a Static Application Security Testing (SAST) tool to detect security vulnerabilities in your code. These tools are operating at code level and don't need an executing environment, and therefore can be executed early in the process, and can be seamlessly integrated in your usual development workflow, during the build or during the code review phases. 
+Use a Static Application Security Testing (SAST) tool to detect security vulnerabilities in your code. These tools are operating at code level and don't need an executing environment, and therefore can be executed early in the process, and can be seamlessly integrated in your usual development workflow, during the build or during the code review phases.
 
-It's like having a skilled expert look over your code repository, helping you find common security vulnerabilities that could be hiding in plain sight as you code. 
+It's like having a skilled expert look over your code repository, helping you find common security vulnerabilities that could be hiding in plain sight as you code.
 
 How to choose your SAST tool?
 Check the license: Some tools are free for open source projects. For example GitHub CodeQL or SemGrep.
@@ -32,23 +32,23 @@ Check the coverage for your language(s)
 
 * Select one that easily integrates with the tools you already use, with your existing process. For example, it's better if the alerts are available as part of your existing code review process and tool, rather than going to another tool to see them.
 * Beware of False Positives! You don't want the tool to slow you down for no reason!
-* Check the features: some tools are very powerful and can do taint tracking (example: GitHub CodeQL), some propose AI-generated fix suggestions, some make it easier to write custom queries (example: SemGrep).  
+* Check the features: some tools are very powerful and can do taint tracking (example: GitHub CodeQL), some propose AI-generated fix suggestions, some make it easier to write custom queries (example: SemGrep).
 
 ## Don't share your secrets
 
 ### Sensitive data, such as API keys, tokens, and passwords, can sometimes accidentally get committed to your repository.
 
-Imagine this scenario: You are the maintainer of a popular open-source project with contributions from developers worldwide. One day, a contributor unknowingly commits to the repository some API keys of a third-party service. Days later, someone finds these keys and uses them to get into the service without permission. The service is compromised, users of your project experience downtime, and your project's reputation takes a hit. As the maintainer, you're now faced with the daunting tasks of revoking compromised secrets, investigating what malicious actions the attacker could have performed with this secret, notifying affected users, and implementing fixes. 
+Imagine this scenario: You are the maintainer of a popular open-source project with contributions from developers worldwide. One day, a contributor unknowingly commits to the repository some API keys of a third-party service. Days later, someone finds these keys and uses them to get into the service without permission. The service is compromised, users of your project experience downtime, and your project's reputation takes a hit. As the maintainer, you're now faced with the daunting tasks of revoking compromised secrets, investigating what malicious actions the attacker could have performed with this secret, notifying affected users, and implementing fixes.
 
-To prevent such incidents, "secret scanning" solutions exist to help you detect those secrets in your code. Some tools like GitHub Secret Scanning, and Trufflehog by Truffle Security can prevent you from pushing them to remote branches in the first place, and some tools will automatically revoke some secrets for you. 
+To prevent such incidents, "secret scanning" solutions exist to help you detect those secrets in your code. Some tools like GitHub Secret Scanning, and Trufflehog by Truffle Security can prevent you from pushing them to remote branches in the first place, and some tools will automatically revoke some secrets for you.
 
 ## Check and update your dependencies
 
 ### Dependencies in your project can have vulnerabilities that compromise the security of your project. Manually keeping dependencies up to date can be a time-consuming task.
 
-Picture this: a project built on the sturdy foundation of a widely-used library. The library later finds a big security problem, but the people who built the application using it don't know about it. Sensitive user data is left exposed when an attacker takes advantage of this weakness, swooping in to grab it. This is not a theoretical case. This is exactly what happened to Equifax in 2017: They failed to update their Apache Struts dependency after the notification that a severe vulnerability was detected. It was exploited, and the infamous Equifax breach affected 144 million users' data. 
+Picture this: a project built on the sturdy foundation of a widely-used library. The library later finds a big security problem, but the people who built the application using it don't know about it. Sensitive user data is left exposed when an attacker takes advantage of this weakness, swooping in to grab it. This is not a theoretical case. This is exactly what happened to Equifax in 2017: They failed to update their Apache Struts dependency after the notification that a severe vulnerability was detected. It was exploited, and the infamous Equifax breach affected 144 million users' data.
 
-To prevent such scenarios, Software Composition Analysis (SCA) tools such as Dependabot and Renovate automatically check your dependencies for known vulnerabilities published in public databases such as the NVD or the GitHub Advisory Database, and then creates pull requests to update them to safe versions. Staying up-to-date with the latest safe dependency versions safeguards your project from potential risks. 
+To prevent such scenarios, Software Composition Analysis (SCA) tools such as Dependabot and Renovate automatically check your dependencies for known vulnerabilities published in public databases such as the NVD or the GitHub Advisory Database, and then creates pull requests to update them to safe versions. Staying up-to-date with the latest safe dependency versions safeguards your project from potential risks.
 
 ## Understand and manage open source license risks
 
@@ -116,10 +116,10 @@ Having a basic incident response plan, even a simple checklist, helps you stay c
 
 Your process doesn't have to be complex. At minimum, define:
 
-* Who reviews and triages security reports or alerts  
-* How severity is evaluated and how mitigation decisions are made  
-* What steps you take to prepare a fix and coordinate disclosure  
-* How you notify affected users, contributors, or downstream consumers 
+* Who reviews and triages security reports or alerts
+* How severity is evaluated and how mitigation decisions are made
+* What steps you take to prepare a fix and coordinate disclosure
+* How you notify affected users, contributors, or downstream consumers
 
 An active incident, if not well managed, can erode trust in your project from your users. Publishing this (or linking to it) in your `SECURITY.md` file can help set expectations and build trust.
 
@@ -153,6 +153,6 @@ Security isn't static. Revisit your processes from time to time. As your project
 
 ### Many thanks to all the maintainers who shared their experiences and tips with us for this guide!
 
-This guide was written by [@nanzggits](https://github.com/nanzggits) & [@xcorail](https://github.com/xcorail) with contributions from: 
+This guide was written by [@nanzggits](https://github.com/nanzggits) & [@xcorail](https://github.com/xcorail) with contributions from:
 
 [@JLLeitschuh](https://github.com/JLLeitschuh), [@intrigus-lgtm](https://github.com/intrigus-lgtm), [@UlisesGascon](https://github.com/ulisesgascon) + many others!
diff --git a/docs/content-model.md b/docs/content-model.md
index 9ef6273b1c4..aea5efbb5cb 100644
--- a/docs/content-model.md
+++ b/docs/content-model.md
@@ -41,4 +41,4 @@ We use bulleted lists to keep articles approachable and skim-able, and to group
 
 - Articles consisting almost entirely of lists; lists should enhance the narrative rather than serve as the main attraction.
 - Exhaustive or canonical lists; follows from above. If such a list is relevant, [link](styleguide.md#content-principles) to one maintained elsewhere.
-- Lists consisting of only links; a guide is not an awesome list. Check out how we link to the main awesome list in a list, [for example](https://opensource.guide/how-to-contribute/#you-dont-just-have-to-work-on-software-projects).
\ No newline at end of file
+- Lists consisting of only links; a guide is not an awesome list. Check out how we link to the main awesome list in a list, [for example](https://opensource.guide/how-to-contribute/#you-dont-just-have-to-work-on-software-projects).