Sentence case migration.

Signed-off-by: Matthew Marchese <maffblaster@gentoo.org>

8 files changed, 72 insertions, 75 deletions

diff --git a/support/documentation/index.html b/support/documentation/index.html
index 2eae34f..1f7fc31 100644
--- a/support/documentation/index.html
+++ b/support/documentation/index.html
@@ -19,14 +19,14 @@ title: 'Documentation'
 </div>
 
 <p>
-  Most of our documentation is available on the <a href="//wiki.gentoo.org">Gentoo Wiki</a>:
+  Most of our documentation is available on the <a href="//wiki.gentoo.org">Gentoo wiki</a>:
 </p>
 
 <div class="row">
   <div class="col-xs-12 col-md-8 col-md-offset-2">
     <div class="panel panel-default">
       <div class="panel-heading">
-        <h3 class="panel-title">Finding Documentation on the <a href="//wiki.gentoo.org">Gentoo Wiki</a></h3>
+        <h3 class="panel-title">Finding documentation on the <a href="//wiki.gentoo.org">Gentoo wiki</a></h3>
       </div>
       <div class="panel-body">
         If you know what you are looking for, you can simply search for one or more keywords:
@@ -41,32 +41,29 @@ title: 'Documentation'
         </form>
 
         <br>
-        Or, browse the Wiki contents using these categories:
+        Or, browse the wiki contents using these categories:
         <br><br>
 
         <div class="list-group" style="font-size: 125%;">
-          <a href="//wiki.gentoo.org/wiki/Category:Core_system" title="Category:Core system" class="list-group-item"><i class="fa fa-fw fa-terminal"></i> Core System</a>
+          <a href="//wiki.gentoo.org/wiki/Category:Core_system" title="Category:Core system" class="list-group-item"><i class="fa fa-fw fa-terminal"></i> Core system</a>
           <a href="//wiki.gentoo.org/wiki/Category:Software" title="Category:Software" class="list-group-item"><i class="fa fa-fw fa-floppy-o"></i> Software</a>
           <a href="//wiki.gentoo.org/wiki/Category:Hardware" title="Category:Hardware" class="list-group-item"><i class="fa fa-fw fa-print"></i> Hardware</a>
           <a href="//wiki.gentoo.org/wiki/Category:Desktop" title="Category:Desktop" class="list-group-item"><i class="fa fa-fw fa-desktop"></i> Desktop</a>
-          <a href="//wiki.gentoo.org/wiki/Category:Server_and_Security" title="Category:Server and Security" class="list-group-item"><i class="fa fa-fw fa-database"></i> Server and Security</a>
-          <a href="//wiki.gentoo.org/wiki/Category:Project_and_Community" title="Category:Project and Community" class="list-group-item"><i class="fa fa-fw fa-institution"></i> Project and Community</a>
+          <a href="//wiki.gentoo.org/wiki/Category:Server_and_Security" title="Category:Server and Security" class="list-group-item"><i class="fa fa-fw fa-database"></i> Server and security</a>
+          <a href="//wiki.gentoo.org/wiki/Category:Project_and_Community" title="Category:Project and Community" class="list-group-item"><i class="fa fa-fw fa-institution"></i> Project and community</a>
         </div>
-
-        <strong>Did you know?</strong>
-        Our documentation team maintains a list of <a href="//wiki.gentoo.org/wiki/Project:Documentation/Overview">featured Wiki articles</a> that are worth a read.
       </div>
     </div>
   </div>
 </div>
 
-<h2>Developer Documentation</h2>
+<h2>Developer documentation</h2>
 
 <p>
-  In addition to the documentation available on the Wiki, we also offer documentation resources geared towards Gentoo development:
+  In addition to the documentation available on the wiki, we also offer documentation resources geared towards Gentoo development:
 </p>
 
 <ul>
-  <li><a href="https://devmanual.gentoo.org/">Gentoo Development Guide</a></li>
-  <li><a href="https://devmanual.gentoo.org/eclass-reference/index.html">eclass Reference</a></li>
-</ul>
\ No newline at end of file
+  <li><a href="https://devmanual.gentoo.org/">Gentoo Development Guide</a> (a.k.a Devmanual).</li>
+  <li><a href="https://devmanual.gentoo.org/eclass-reference/index.html">Online eclass reference</a>.</li>
+</ul>
diff --git a/support/index.html b/support/index.html
index 4e78445..60859ce 100644
--- a/support/index.html
+++ b/support/index.html
@@ -8,7 +8,7 @@ title: 'Support'
 <br>
 <div class="panel panel-default">
   <div class="panel-heading">
-    <h3 class="panel-title"><span class="fa fa-fw fa-life-buoy"></span> Getting Help with your Gentoo System</h3>
+    <h3 class="panel-title"><span class="fa fa-fw fa-life-buoy"></span> Getting help with Gentoo</h3>
   </div>
   <div class="panel-body">
     <p>
@@ -19,11 +19,11 @@ title: 'Support'
       We advise you to seek answers to your support questions in the following documentation resources and support venues:
     </p>
     <div class="list-group large">
-      <a href="https://wiki.gentoo.org/wiki/FAQ" class="list-group-item"><i class="fa fa-fw fa-question-circle"></i> Frequently Asked Questions</a>
+      <a href="https://wiki.gentoo.org/wiki/FAQ" class="list-group-item"><i class="fa fa-fw fa-question-circle"></i> Frequently asked questions</a>
       <a href="/support/documentation/" class="list-group-item"><i class="fa fa-fw fa-book"></i> Documentation</a>
-      <a href="/get-involved/irc-channels/" class="list-group-item"><i class="fa fa-fw fa-comments-o"></i> IRC Channels</a>
+      <a href="/get-involved/irc-channels/" class="list-group-item"><i class="fa fa-fw fa-comments-o"></i> IRC channels</a>
       <a href="https://forums.gentoo.org/" class="list-group-item"><i class="fa fa-fw fa-users"></i> Forums</a>
-      <a href="/get-involved/mailing-lists/" class="list-group-item"><i class="fa fa-fw fa-inbox"></i> Mailing Lists</a>
+      <a href="/get-involved/mailing-lists/" class="list-group-item"><i class="fa fa-fw fa-inbox"></i> Mailing lists</a>
     </div>
 
     Many Gentoo developers frequently visit those community channels and try their best to contribute to the ongoing discussions and questions.
@@ -32,7 +32,7 @@ title: 'Support'
 
 <div class="panel panel-default">
   <div class="panel-heading">
-    <h3 class="panel-title"><span class="fa fa-fw fa-laptop"></span> Hardware Requirements</h3>
+    <h3 class="panel-title"><span class="fa fa-fw fa-laptop"></span> Hardware requirements</h3>
   </div>
   <div class="panel-body">
     The hardware requirements for each architecture are placed in our <a href="https://wiki.gentoo.org/wiki/Handbook:Main_Page">Gentoo Handbook</a>,
@@ -42,7 +42,7 @@ title: 'Support'
 
 <div class="panel panel-default">
   <div class="panel-heading">
-    <h3 class="panel-title"><span class="fa fa-fw fa-bug"></span> Reporting Bugs</h3>
+    <h3 class="panel-title"><span class="fa fa-fw fa-bug"></span> Reporting bugs</h3>
   </div>
   <div class="panel-body">
     <p>
diff --git a/support/news-items/index.html b/support/news-items/index.html
index 5cf8701..06527c6 100644
--- a/support/news-items/index.html
+++ b/support/news-items/index.html
@@ -1,6 +1,6 @@
 ---
-title: 'Repository News Items'
-navtitle: 'News Items'
+title: 'Repository news items'
+navtitle: 'News items'
 
 nav1: support
 
@@ -8,16 +8,16 @@ nav2: news-items
 nav2-show: true
 ---
 <p class="lead">
-  Important news regarding packages available in Gentoo are published via <em>news items</em>. You can find them below.
+  Important news regarding packages available in Gentoo are published via <em>news items</em>. They can be found below.
 </p>
 
 <div class="alert alert-info">
   <strong>Which items affect me?</strong>
   <p>
-  This page lists <strong>all</strong> available news items for the official Gentoo package repository, but sometimes items don't affect you because you don't have the relevant package installed,
+  This page lists <strong>all</strong> available news items for the official Gentoo ebuild repository, but sometimes items don't affect you because you don't have the relevant package installed,
   or use a different architecture.
   <br>
-  The <kbd>emerge</kbd> command notifies you after each operation if there are news items affecting your configuration:
+  The <kbd>emerge</kbd> command provides notifications after each operation if there are news items affecting the system configuration:
   </p>
   <p>
   <pre>
@@ -31,7 +31,7 @@ nav2-show: true
   For more information on the "Critical News" publication system, please see <a href="https://wiki.gentoo.org/wiki/GLEP:42">GLEP 42</a>.
 </p>
 
-<h2>Published News Items</h2>
+<h2>Published news items</h2>
 
 <table class="table table-condensed table-striped">
   <tr>
diff --git a/support/package-database.html b/support/package-database.html
index 2668a00..5abf60d 100644
--- a/support/package-database.html
+++ b/support/package-database.html
@@ -1,5 +1,5 @@
 ---
-title: 'Package Database'
+title: 'Package database'
 nav1: support
 nav2: package-database
 nav2-show: true
diff --git a/support/rsync-mirrors/index.html b/support/rsync-mirrors/index.html
index 38fd327..361a064 100644
--- a/support/rsync-mirrors/index.html
+++ b/support/rsync-mirrors/index.html
@@ -1,6 +1,6 @@
 ---
-title: 'Gentoo rsync Mirrors'
-navtitle: 'rsync Mirrors'
+title: 'Gentoo rsync mirrors'
+navtitle: 'rsync mirrors'
 nav1: support
 nav2: mirrors
 nav2-show: true
@@ -8,22 +8,22 @@ nav2-show: true
 
 <p>
   Gentoo is hosted by many mirrors around the globe.
-  Selecting a mirror that is geographically near you may help speed up Portage tree updates.
+  Selecting a mirror that is geographically near may help speed up repository syncs.
 </p>
 
 <div class="alert alert-info">
-  <strong>Using rsync Mirrors</strong>
+  <strong>Using rsync mirrors</strong>
   <br />
-  The mirrors listed <strong>on this page</strong> are used for updating your Portage tree.
+  The mirrors listed <strong>on this page</strong> are used for updating the Gentoo ebuild repository.
   <br />
   To use an rsync mirror, set the <tt>sync-uri</tt> variable in the <tt>[gentoo]</tt> section of <tt>repos.conf</tt> to a URL from the list below.
-  <a href="https://wiki.gentoo.org/wiki//etc/portage/repos.conf/gentoo.conf" class="alert-link">More information</a> is available in our Wiki.
+  <a href="https://wiki.gentoo.org/wiki//etc/portage/repos.conf/gentoo.conf" class="alert-link">More information</a> is available on the wiki.
 </div>
 
 <div class="alert alert-success">
-  <strong>Source Mirrors</strong>
+  <strong>Source (distfile) mirrors</strong>
   <br />
-  We also have a second type of mirrors that you use for fetching installation files as well as package sources (configured via <code>GENTOO_MIRRORS</code>).
+  We also have a second type of mirrors that you use for fetching installation files as well as package sources (configured via <var>GENTOO_MIRRORS</var> variable in <tt>make.conf</tt>).
   They are available on a <a href="/downloads/mirrors/" class="alert-link">separate page</a>.
 </div>
 
@@ -34,12 +34,12 @@ nav2-show: true
 </div>
 
 <p>
-  We would like to thank the many organizations and individuals that are providing mirroring services to the Gentoo project. If you would like to contribute a mirror, please consult the <a href="https://wiki.gentoo.org/wiki/Project:Infrastructure/Mirrors/Rsync">relevant documentation</a>.
+We would like to thank the <i>many</i> organizations and individuals that are providing mirroring services to the Gentoo project. If you would like to contribute a mirror, please consult the <a href="https://wiki.gentoo.org/wiki/Project:Infrastructure/Mirrors/Rsync">relevant documentation</a>.
 </p>
 
 <hr>
 
-<h2>Countries covered by Gentoo rsync Mirrors</h2>
+<h2>Countries covered by Gentoo rsync mirrors</h2>
 
 <table class="table table-condensed table-striped">
   <tr>
diff --git a/support/security/index.html b/support/security/index.html
index 994348f..c5ed46e 100644
--- a/support/security/index.html
+++ b/support/security/index.html
@@ -1,5 +1,5 @@
 ---
-title: 'Gentoo Security'
+title: 'Gentoo security'
 navtitle: 'Security'
 nav1: support
 nav2: security
@@ -16,7 +16,7 @@ layout: page-nav3
 
 <p>
   Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users machines is of utmost importance to us.
-  The <a href="https://wiki.gentoo.org/wiki/Project:Security">Gentoo Linux Security Project</a>
+  The <a href="https://wiki.gentoo.org/wiki/Project:Security">Security Project</a>
   is tasked with providing timely information about security vulnerabilities in Gentoo Linux, along with patches to secure those vulnerabilities.
   We work directly with vendors, end users and other OSS projects to ensure all security incidents are responded to quickly and professionally.
 </p>
@@ -32,7 +32,7 @@ layout: page-nav3
   for building a secure system and hardening existing systems.
 </p>
 
-<h3>Keeping your Gentoo system secure</h3>
+<h3>Keeping Gentoo secure</h3>
 <p>
   To stay up-to-date with the security fixes you should subscribe to receive GLSAs and apply GLSA instructions whenever you have an affected package installed.
   Alternatively, syncing your portage tree and upgrading every package should also keep you up-to-date security-wise.
@@ -52,7 +52,7 @@ layout: page-nav3
   Gentoo Linux Security Announcements are notifications that we send out to the community to inform them of security vulnerabilities related to Gentoo Linux or the packages contained in our portage repository.
 </p>
 
-<h3>Recent Advisories</h3>
+<h3>Recent advisories</h3>
 
 {% include frontpage/glsa %}
 
@@ -65,7 +65,7 @@ layout: page-nav3
   GLSA announcements are sent to the <a href="/get-involved/mailing-lists/">gentoo-announce@gentoo.org mailing-list</a>, and are published via <a href="https://security.gentoo.org/subscribe">RSS and Atom feeds</a>.
 </p>
 
-<h3 id="contact">Security Team contact information</h3>
+<h3 id="contact">Security team contact information</h3>
 <p>
   Gentoo Linux takes security vulnerability reports very seriously.
   Please file new vulnerability reports on <a href="https://bugs.gentoo.org">Gentoo Bugzilla</a>
@@ -78,13 +78,13 @@ layout: page-nav3
 </p>
 
 <p>
-  <a href="https://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%20Security&amp;component=Vulnerabilities" class="btn btn-primary btn-sm"><span class="fa fa-fw fa-bug"></span> Report Security Vulnerability</a>
-  <a href="https://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%20Security&amp;component=GLSA%20Errors" class="btn btn-primary btn-sm"><span class="fa fa-fw fa-bug"></span> Report GLSA Error</a>
+  <a href="https://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%20Security&amp;component=Vulnerabilities" class="btn btn-primary btn-sm"><span class="fa fa-fw fa-bug"></span> Report security vulnerability</a>
+  <a href="https://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%20Security&amp;component=GLSA%20Errors" class="btn btn-primary btn-sm"><span class="fa fa-fw fa-bug"></span> Report GLSA error</a>
 </p>
 
 <h3>Confidential contacts</h3>
 <p>
-  You have two options to submit non-public vulnerabilities to the Gentoo Linux Security Team.
+  You have two options to submit non-public vulnerabilities to the security team.
   You may submit a bug in <a href="https://bugs.gentoo.org/">Gentoo Bugzilla</a> using the <em>New-Expert</em> action, or the <em>Enter a new bug report (advanced)</em> link,
   and check the <em>Gentoo Security</em> checkbox in the <em>Only users in all of the selected groups can view this bug</em> section.
   You may also contact directly using encrypted mail one of the following security contacts:
@@ -94,11 +94,11 @@ layout: page-nav3
   <td class="infohead"><b>Name</b></td>
   <td class="infohead"><b>Responsibility</b></td>
   <td class="infohead"><b>Email</b></td>
-  <td class="infohead"><b>GPG keyID (click to retrieve public key)</b></td>
+  <td class="infohead"><b>GPG key ID (click to retrieve public key)</b></td>
 </tr>
 <tr>
   <td class="tableinfo">Yury German</td>
-  <td class="tableinfo">Security team lead</td>
+  <td class="tableinfo">Security lead</td>
   <td class="tableinfo"><a href="mailto:blueknight@gentoo.org">blueknight@gentoo.org</a></td>
   <td class="tableinfo"><a href="https://pgp.mit.edu/pks/lookup?op=get&search=0xEEAFED89024C043D">0xEEAFED89024C043D</a></td>
 </tr>
@@ -110,7 +110,7 @@ layout: page-nav3
 </tr>
 <tr>
   <td class="tableinfo">Jason A. Donenfeld</td>
-  <td class="tableinfo">Security Auditing Lead</td>
+  <td class="tableinfo">Security auditing lead</td>
   <td class="tableinfo"><a href="mailto:zx2c4@gentoo.org">zx2c4@gentoo.org</a></td>
   <td class="tableinfo"><a href="http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x49FC7012A5DE03AE">0x49FC7012A5DE03AE</a></td>
 </tr>
@@ -125,15 +125,15 @@ layout: page-nav3
 
 <h3>Security pages</h3>
 <ul>
-  <li><a href="https://security.gentoo.org/glsa/">GLSA index page</a> — Full list of all published GLSAs</li>
+  <li><a href="https://security.gentoo.org/glsa/">GLSA index page</a> — Full list of all published GLSAs.</li>
   <li><a href="https://security.gentoo.org/glsa/feed.rss">GLSA RSS feed</a> — GLSA RSS live feed.</li>
-  <li><a href="vulnerability-treatment-policy.html">Vulnerability Treatment Policy</a> — The official policy the Security Team follows</li>
-  <li><a href="https://wiki.gentoo.org/wiki/Project:Security">Gentoo Linux Security Project</a> — The security project page</li>
+  <li><a href="vulnerability-treatment-policy.html">Vulnerability Treatment Policy</a> — The official policy of the security team.</li>
+  <li><a href="https://wiki.gentoo.org/wiki/Project:Security">Gentoo Linux Security Project</a> — The security project page.</li>
 </ul>
 
 <h3>Links</h3>
 <ul>
-  <li><a href="https://wiki.gentoo.org/wiki/Security_Handbook">Gentoo Security Handbook</a> — Step-by-step guide for hardening Gentoo Linux</li>
-  <li><a href="https://wiki.gentoo.org/wiki/Project:Hardened">Gentoo Hardened Project</a> — Bringing advanced security to Gentoo Linux</li>
-  <li><a href="/inside-gentoo/developers/">Active Developer List</a> — Active Developer List including GPG keys which can be used to verify GLSAs</li>
+  <li><a href="https://wiki.gentoo.org/wiki/Security_Handbook">Gentoo Security Handbook</a> — Step-by-step guide for hardening Gentoo Linux.</li>
+  <li><a href="https://wiki.gentoo.org/wiki/Project:Hardened">Gentoo Hardened Project</a> — Bringing advanced security to Gentoo Linux.</li>
+  <li><a href="/inside-gentoo/developers/">Active Developer List</a> — Active developer list including GPG keys which can be used to verify GLSAs.</li>
 </ul>
diff --git a/support/security/vulnerability-treatment-policy.html b/support/security/vulnerability-treatment-policy.html
index 9fec74d..bc4955e 100644
--- a/support/security/vulnerability-treatment-policy.html
+++ b/support/security/vulnerability-treatment-policy.html
@@ -21,7 +21,7 @@ body_class: nav-align-h2
 </p>
 
 <p>
-  For this reason, the Security Team separates Gentoo architectures into two groups, <strong>supported</strong> and <strong>unsupported:</strong>
+  For this reason, the security team separates Gentoo architectures into two groups, <strong>supported</strong> and <strong>unsupported:</strong>
 </p>
 
 <dl>
@@ -67,7 +67,7 @@ body_class: nav-align-h2
   <strong>Note:</strong> This policy might be changed when our tools support more complex upgrade paths and if a sufficient number of GLSA coordinators join the Security Team.
 </div>
 
-<h2>Vulnerability Feed</h2>
+<h2>Vulnerability feed</h2>
 
 <h3>Published vulnerabilities</h3>
 <p>
@@ -94,7 +94,7 @@ body_class: nav-align-h2
 
 <h2>Dispatch</h2>
 
-<h3>Severity Level</h3>
+<h3>Severity level</h3>
 <p>
   In order to seed the appropriate reaction times and escalation procedures, we need to assign a severity level to each vulnerability.
   This severity level must be based on how widespread the affected software is amongst Gentoo users and depth of the vulnerability.
@@ -275,20 +275,20 @@ You can use the following two tables to help you assign the severity level:
 
 <h2>Bug correction and GLSA draft</h2>
 
-<h3>GLSA Coordinator role</h3>
+<h3>GLSA coordinator role</h3>
 <p>
   The GLSA coordinator has responsibility for the following tasks:
 </p>
 
 <ul>
-  <li>determine what must be done in order to close the vulnerability (for example identify the upstream version containing the fix)</li>
-  <li>if no fix is available from upstream yet, ensure that the bug is correctly reported to the upstream developer and set status whiteboard to <code>upstream</code></li>
-  <li>if a fix is available, get the package maintainer involved to produce and commit an ebuild containing the fix and set status whiteboard to <code>ebuild</code></li>
-  <li>once an ebuild is committed, evaluate what keywords are needed for the fix ebuild
-  and get arch-specific Teams to test and mark the ebuild stable on their architectures (arch teams should be cc'd on the bug, as well as releng during release preparation) and set status whiteboard to <code>stable</code></li>
-  <li>arch-maintainers should mark the ebuild stable if there is no regression in the fix ebuild compared to the latest vulnerable version</li>
-  <li>in parallel, writing a draft GLSA using the GLSAMaker tool</li>
-  <li>when the corrective ebuild is ready for all supported archs, set the status whiteboard to <code>glsa</code></li>
+  <li>Determine what must be done in order to close the vulnerability (for example identify the upstream version containing the fix).</li>
+  <li>If no fix is available from upstream yet, ensure that the bug is correctly reported to the upstream developer and set status whiteboard to <code>upstream</code>.</li>
+  <li>If a fix is available, get the package maintainer involved to produce and commit an ebuild containing the fix and set status whiteboard to <code>ebuild</code>.</li>
+  <li>Once an ebuild is committed, evaluate what keywords are needed for the fix ebuild
+  and get arch-specific Teams to test and mark the ebuild stable on their architectures (arch teams should be cc'd on the bug, as well as releng during release preparation) and set status whiteboard to <code>stable</code>.</li>
+  <li>Arch-maintainers should mark the ebuild stable if there is no regression in the fix ebuild compared to the latest vulnerable version.</li>
+  <li>In parallel, writing a draft GLSA using the GLSAMaker tool.</li>
+  <li>When the corrective ebuild is ready for all supported archs, set the status whiteboard to <code>glsa</code>.</li>
 </ul>
 
 <div class="alert alert-info">
@@ -326,7 +326,7 @@ You can use the following two tables to help you assign the severity level:
   <li>Vulnerable versions should be left in the tree until the bug enters the <code>stable</code> status, in order to correctly evaluate what keywords are needed for the fix version</li>
 </ul>
 
-<h2>GLSA Publication Process</h2>
+<h2>GLSA publication process</h2>
 
 <h3>Peer review</h3>
 <p>
@@ -370,7 +370,7 @@ You can use the following two tables to help you assign the severity level:
 
 <div class="alert alert-info">
   <strong>Notes:</strong><br>
-  Developer key IDs can be found on the Gentoo Linux <a href="/inside-gentoo/developers/">Developer list</a>. All the Security Team GPG keys are published on public key servers, including (but not limited to) <a href="http://subkeys.pgp.net:11371">subkeys.pgp.net</a>.<br>
+  Developer key IDs can be found in the Gentoo Linux <a href="/inside-gentoo/developers/">Developer list</a>. All the security team GPG keys are published on public key servers, including (but not limited to) <a href="http://subkeys.pgp.net:11371">subkeys.pgp.net</a>.<br>
 
   To minimize errors in the publication process, the forum publication step is handled by an automatic poster when it receives the announcement.<br>
 
@@ -384,7 +384,7 @@ You can use the following two tables to help you assign the severity level:
   GLSAMaker 2 offers this option after releasing the advisory.
 </p>
 
-<h3>GLSA Errata</h3>
+<h3>GLSA errata</h3>
 <p>
   Sometimes an error will slip through the peer-review process and an incorrect GLSA will be published to the world. Depending on the severity of the error(s), the following policy for erratum should be applied:
 </p>
@@ -418,4 +418,4 @@ You can use the following two tables to help you assign the severity level:
     <td>Error in affected/unaffected versions number, people applying GLSA instructions are not at all protected</td>
     <td>An erratum GLSA should be published, replacing the erroneous one</td>
   </tr>
-</table>
\ No newline at end of file
+</table>
diff --git a/support/use-flags/index.html b/support/use-flags/index.html
index 140706f..86d8d8e 100644
--- a/support/use-flags/index.html
+++ b/support/use-flags/index.html
@@ -1,6 +1,6 @@
 ---
-title: 'USE Flag Index'
-navtitle: 'USE Flags'
+title: 'USE flag index'
+navtitle: 'USE flags'
 nav1: support
 nav2: use
 nav2-show: true
@@ -15,7 +15,7 @@ nav2-show: true
 
 <hr>
 
-<h2 id="global">Global USE Flags</h2>
+<h2 id="global">Global USE flags</h2>
 
 <table class="table table-condensed table-striped">
   <tr>
@@ -30,7 +30,7 @@ nav2-show: true
 {% endfor %}
 </table>
 
-<h2 id="local">Local USE Flags</h2>
+<h2 id="local">Local USE flags</h2>
 
 {% for category in site.data.use.local %}
   <h3 id="{{ category[0] }}">{{ category[0] }}</h3>
@@ -47,4 +47,4 @@ nav2-show: true
     {% endfor %}
     </table>
   {% endfor %}
-{% endfor %}
\ No newline at end of file
+{% endfor %}