Merge pull request #218 from jbampton/fix-spelling

docs: fix spelling

Author: clambertus

content/asciidocs/continuous-improvement.adoc

@@ -43,7 +43,7 @@ TODO: gmcdonald:
 * better arm support
 * ephemeral nodes for jenkins
 * build caching
-* better github actions support
+* better GitHub actions support
 
 [.notes]
 --

content/blog/downtime_notice_for_the_r.md

@@ -3,4 +3,4 @@ date: '2015-01-12T15:02:12+00:00'
 permalink: downtime_notice_for_the_r
 layout: post
 
-<span style="color: #222222; font-family: arial, sans-serif;">Folks,</span><br style="color: #222222; font-family: arial, sans-serif;" /><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">Please note than on Thursday 15th at 20:00 UTC the Infrastructure team</span><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">will be taking the read/write git repositories offline.&nbsp; We expect</span><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">that this migration to last about 4 hours.</span><br style="color: #222222; font-family: arial, sans-serif;" /><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">During the outage the service will be migrated from an old host to a</span><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">new one.&nbsp; &nbsp;We intend to keep the URL the same for access to the repos</span><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">after the migration, but an alternate name is already in place in case</span><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">DNS updates take too long.&nbsp; &nbsp;Please be aware it might take some hours</span><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">after the completion of the downtime for github to update and reflect</span><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">any changes.</span><br style="color: #222222; font-family: arial, sans-serif;" /><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">The Infrastructure team have been trialling the new host for about a</span><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">week now, and [touch wood] have not had any problems with it.</span><br style="color: #222222; font-family: arial, sans-serif;" /><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">The service is current;y available by accessing repos via:</span><br style="color: #222222; font-family: arial, sans-serif;" /><a href="https://git-wip-us.apache.org/" target="_blank" style="color: #1155cc; font-family: arial, sans-serif;">https://git-wip-us.apache.org</a><br style="color: #222222; font-family: arial, sans-serif;" /><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">If you have any questions please address them to </span><a href="mailto:[email protected]" title="[GMCP] Compose a new mail to [email protected]" rel="noreferrer" style="color: #1155cc; font-family: arial, sans-serif;">[email protected]</a><br style="color: #222222; font-family: arial, sans-serif;" /><br style="color: #222222; font-family: arial, sans-serif;" />
+<span style="color: #222222; font-family: arial, sans-serif;">Folks,</span><br style="color: #222222; font-family: arial, sans-serif;" /><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">Please note than on Thursday 15th at 20:00 UTC the Infrastructure team</span><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">will be taking the read/write git repositories offline.&nbsp; We expect</span><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">that this migration to last about 4 hours.</span><br style="color: #222222; font-family: arial, sans-serif;" /><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">During the outage the service will be migrated from an old host to a</span><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">new one.&nbsp; &nbsp;We intend to keep the URL the same for access to the repos</span><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">after the migration, but an alternate name is already in place in case</span><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">DNS updates take too long.&nbsp; &nbsp;Please be aware it might take some hours</span><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">after the completion of the downtime for GitHub to update and reflect</span><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">any changes.</span><br style="color: #222222; font-family: arial, sans-serif;" /><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">The Infrastructure team have been trialling the new host for about a</span><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">week now, and [touch wood] have not had any problems with it.</span><br style="color: #222222; font-family: arial, sans-serif;" /><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">The service is currently available by accessing repos via:</span><br style="color: #222222; font-family: arial, sans-serif;" /><a href="https://git-wip-us.apache.org/" target="_blank" style="color: #1155cc; font-family: arial, sans-serif;">https://git-wip-us.apache.org</a><br style="color: #222222; font-family: arial, sans-serif;" /><br style="color: #222222; font-family: arial, sans-serif;" /><span style="color: #222222; font-family: arial, sans-serif;">If you have any questions please address them to </span><a href="mailto:[email protected]" title="[GMCP] Compose a new mail to [email protected]" rel="noreferrer" style="color: #1155cc; font-family: arial, sans-serif;">[email protected]</a><br style="color: #222222; font-family: arial, sans-serif;" /><br style="color: #222222; font-family: arial, sans-serif;" />

content/blog/new-notification-scheme-features-for.md

@@ -5,4 +5,4 @@ layout: post
 
 <p>Today, ASF Infra launched new features for projects wishing to update their notification schemes for git/github activity on their own.</p>
 <p>Via the <a href="https://infra.apache.org/asf-yaml.html" target="_blank">.asf.yaml</a> file, projects can now define notification schemes for their repositories, including targets for commit emails, GitHub events, and Jira notification options.</p>
-<p>Along with this notification scheme feature, we have also launched some corrective measures for repositories where github activity did not result in proper relaying to our mailing lists, so some projects may start seeing event messages that did not appear before. Furthermore, we are now combining review comments into single emails, to lessen the load in your inbox.</p><p><br></p><p>With regards,</p><p>The ASF Infrastructure Team.<br></p>
+<p>Along with this notification scheme feature, we have also launched some corrective measures for repositories where GitHub activity did not result in proper relaying to our mailing lists, so some projects may start seeing event messages that did not appear before. Furthermore, we are now combining review comments into single emails, to lessen the load in your inbox.</p><p><br></p><p>With regards,</p><p>The ASF Infrastructure Team.<br></p>

content/blog/relocation-of-apache-git-repositories.md

@@ -3,7 +3,7 @@ date: '2018-12-07T17:33:33+00:00'
 permalink: relocation-of-apache-git-repositories
 layout: post
 
-<p>[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE DISREGARD THIS POST]<br /><br />Hello Apache projects,<br /><br />I am writing to you because you may have git repositories on the git-wip-us server, which is slated to be decommissioned in the coming months. All repositories will be moved to the new gitbox service which includes direct write access on github as well as the standard ASF commit access via gitbox.apache.org.</p> 
+<p>[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE DISREGARD THIS POST]<br /><br />Hello Apache projects,<br /><br />I am writing to you because you may have git repositories on the git-wip-us server, which is slated to be decommissioned in the coming months. All repositories will be moved to the new gitbox service which includes direct write access on GitHub as well as the standard ASF commit access via gitbox.apache.org.</p> 
   <p><strong>Why this move?</strong><br />The move comes as a result of retiring the git-wip service, as the hardware it runs on is longing for retirement. In lieu of this, we have decided to consolidate the two services (git-wip and gitbox), to ease the management of our repository systems and future-proof the underlying hardware. The move is fully automated, and ideally, nothing will change in your workflow other than added features and access to GitHub.<br /></p> 
   <p><strong>Timeframe for relocation</strong><br />Initially, we are asking that projects voluntarily request to move their repositories to gitbox. The voluntary time frame is between now and January 9th 2019, during which projects are free to either move over to gitbox or stay put on git-wip. After this phase, we will be requiring the remaining projects to move within one month, after which we will move the remaining projects over.<br /><br />To have your project moved in this initial phase, you will need:<br /></p> 
   <ul> 

content/pages/backup-policy.md

@@ -14,7 +14,7 @@ Foundation Critical systems receive additional nightly rsync/zfs based snapshots
   - /x1/db_dump is picked up by the rsync or backuppc process
 
 #### Software repositories ####
-  - gitbox.a.o (rsync, backuppc, github mirrors).
+  - gitbox.a.o (rsync, backuppc, GitHub mirrors).
   - svn.a.o (rsync, backuppc, azure DR replica).
   - archive.a.o (backuppc).
 

content/pages/infra-incubator.md

@@ -53,7 +53,7 @@ It takes about twelve hours after the mentor makes the request before the mailin
 
 Moving existing repositories into ASF version control generally requires a github.com transition to the `github.com/apache/` organization. To make the transition,, file a Jira ticket with Infra.
 
-If you wish to copy existing code without transferring github stars, etc., your mentor can request **new repositories** for the project via <a href="https://selfserve.apache.org/" target="_blank">SelfServe</a>.
+If you wish to copy existing code without transferring GitHub stars, etc., your mentor can request **new repositories** for the project via <a href="https://selfserve.apache.org/" target="_blank">SelfServe</a>.
 
 
 **Bug tracking**

content/pages/version-control.md

@@ -59,7 +59,7 @@ Each PMC can have **one** private Git repository. Open a Jira ticket for Infra t
 Projects can also place `.asf.yaml` in the root of a repository to control:
 
 -  notification settings
--  github settings
+-  GitHub settings
 -  pelican builds
 
 Read [the .asf.yaml primer](asf-yaml.html) to learn more.