Merge pull request #220 from jbampton/fix-spelling

docs: fix spelling / word casing

Author: cottage14

content/blog/README.md

@@ -25,7 +25,7 @@ These metadata fields are available, but are currently optional for the Infra bl
   - status: options are `draft`, `hidden`, or `published`
   - summary: brief description for use on index pages
   - tags: content tags, separated by commas
-  - url: url to use for this article
+  - url: URL to use for this article
 
 Pelican supports these tags, which the Infra blog does not use:
 

content/blog/apache_cms_new_features_for.md

@@ -10,7 +10,7 @@ Links to suggestions for setting up a project website, and website guidelines, a
 <hr/>
 
 <p>Two new features have recently been added to the CMS, courtesy of David Blevins.&nbsp; These features are geared towards streamlining the user experience for <a href="http://www.apache.org/dev/cmsref#non-committer">anonymous users</a>.&nbsp; The first feature is &quot;Quick Mail&quot;, which is the analog of &quot;Quick Commit&quot; but for anonymous users who cannot otherwise commit their changes directly.&nbsp; Quick Mail, which is enabled by default, will take the immediate submission of an anonymous Edit session and post it directly to the project's dev list, saving several steps that might be hard for a new user to walk through.</p> 
-  <p>The second feature is a natural result of that known as anonymous clones.&nbsp; In the subsequent mailout from &quot;Quick Mail&quot;, there will be an url for committers to use to effectively clone the working copy of the anonymous user who generated the patch.&nbsp; This makes review and subsequent commit operations much more convenient than directly applying the emailed patch to a local working copy.&nbsp; In fact it is possible for users to clone a non-anonymous user's working copy, so anyone experiencing chronic problems with their working copy on the CMS can get help from other committers by simply using the &quot;Mail Diff&quot; feature to contact either the dev list or another apache committer with details of their problem.</p> 
+  <p>The second feature is a natural result of that known as anonymous clones.&nbsp; In the subsequent mailout from &quot;Quick Mail&quot;, there will be an URL for committers to use to effectively clone the working copy of the anonymous user who generated the patch.&nbsp; This makes review and subsequent commit operations much more convenient than directly applying the emailed patch to a local working copy.&nbsp; In fact it is possible for users to clone a non-anonymous user's working copy, so anyone experiencing chronic problems with their working copy on the CMS can get help from other committers by simply using the &quot;Mail Diff&quot; feature to contact either the dev list or another apache committer with details of their problem.</p> 
   <p>We have added these features in the hopes this will considerably lower the bar for anonymous users in particular to take advantage of the CMS.&nbsp; Please let your community know about them!</p> 
   <p><br /></p> 
   <p><br /></p>

content/blog/public_preview_of_drafts_feature.md

@@ -7,4 +7,4 @@ layout: post
 **Note**: Until June, 2023, the ASF supported using Apache Roller for project blogs. That support has ended. Please visit <a href="https://infra.apache.org/project-blogs.html" target="_blank">Project Blog</a> for more information about blogs for projects.
 <hr/>
 
-<p>Previously, to be able to preview a draft post by any Roller Blog, one had to be a member user of that blog.</p><p>For those that would like an easy way to post previews of drafts for lazy consensus or voting, a script has been setup to allow the preview url that Roller generates to be shared publicly. &nbsp;For example:</p><p>&nbsp;&nbsp; (roller preview url)<br />&nbsp;&nbsp; &nbsp;<span class="Apple-style-span" style="color: rgb(34, 34, 34); font-family: 'Helvetica Neue'; font-size: 13px; "><a href="https://blogs.apache.org/roller-ui/authoring/preview/test/?previewEntry=testing">https://blogs.apache.org/roller-ui/authoring/preview/test/?previewEntry=testing</a></span></p><p>&nbsp;&nbsp; (public preview url)<br />&nbsp;&nbsp; &nbsp;<a href="https://blogs.apache.org/preview/test/?previewEntry=testing"><span class="Apple-style-span" style="font-size: small; ">https://blogs.apache.org/preview/test/?previewEntry=testing</span></a></p><p>A typical process is to create the blog post, set it up to publish in&nbsp;3-4 days via the &quot;Advanced Settings&quot;, then post the modified preview URL to your dev@ list with the anticipated publish date for lazy consensus.</p><p>Projects must opt-in by adding the &quot;preview&quot; user with &quot;Limited&quot; access.</p><p>Details here:</p><p><a href="http://www.apache.org/dev/blogs.html">http://www.apache.org/dev/blogs.html&nbsp;</a></p>
+<p>Previously, to be able to preview a draft post by any Roller Blog, one had to be a member user of that blog.</p><p>For those that would like an easy way to post previews of drafts for lazy consensus or voting, a script has been setup to allow the preview URL that Roller generates to be shared publicly. &nbsp;For example:</p><p>&nbsp;&nbsp; (roller preview url)<br />&nbsp;&nbsp; &nbsp;<span class="Apple-style-span" style="color: rgb(34, 34, 34); font-family: 'Helvetica Neue'; font-size: 13px; "><a href="https://blogs.apache.org/roller-ui/authoring/preview/test/?previewEntry=testing">https://blogs.apache.org/roller-ui/authoring/preview/test/?previewEntry=testing</a></span></p><p>&nbsp;&nbsp; (public preview url)<br />&nbsp;&nbsp; &nbsp;<a href="https://blogs.apache.org/preview/test/?previewEntry=testing"><span class="Apple-style-span" style="font-size: small; ">https://blogs.apache.org/preview/test/?previewEntry=testing</span></a></p><p>A typical process is to create the blog post, set it up to publish in&nbsp;3-4 days via the &quot;Advanced Settings&quot;, then post the modified preview URL to your dev@ list with the anticipated publish date for lazy consensus.</p><p>Projects must opt-in by adding the &quot;preview&quot; user with &quot;Limited&quot; access.</p><p>Details here:</p><p><a href="http://www.apache.org/dev/blogs.html">http://www.apache.org/dev/blogs.html&nbsp;</a></p>

content/blog/s_apache_org_uri_shortening.md

@@ -4,10 +4,10 @@ permalink: s_apache_org_uri_shortening
 layout: post
 
 <p>
-Today we've brought <a href="http://s.apache.org/">s.apache.org</a> online.  It's a url shortening service that's limited to Apache committers- the people who write all that Apache software!   One of the main reasons we're providing this service is to allow committers to use shortened links whose provenance is known to be a trusted source, which is a big improvement over the generic shorteners out there in the wild.  It is also meant to provide permanent links suitable for inclusion in board reports, or more generally email sent to our mailing lists - which will be archived, either publicly or privately, for as long as Apache is around.
+Today we've brought <a href="http://s.apache.org/">s.apache.org</a> online.  It's a URL shortening service that's limited to Apache committers- the people who write all that Apache software!   One of the main reasons we're providing this service is to allow committers to use shortened links whose provenance is known to be a trusted source, which is a big improvement over the generic shorteners out there in the wild.  It is also meant to provide permanent links suitable for inclusion in board reports, or more generally email sent to our mailing lists - which will be archived, either publicly or privately, for as long as Apache is around.
 </p> 
   <p>
 The service is easy to use, and being from Apache the <a href="http://s.apache.org?action=source">source code</a> for the service is readily available.    The primary author of the code is Ulrich Stärk (uli).  Some of the more interesting features you can pick up from the source is the ability to &quot;display&quot; a link before doing a redirect by tacking on &quot;?action=display&quot; to any shortened url. For the truly paranoid there is the &quot;?action=display;cookie=1&quot; query string to force <strong>all</strong> shortened urls to display by default before redirecting. That feature may be turned off again with the &quot;?action=display;cookie=&quot; query string.  Again, look over the source code for other interesting features you may wish to take advantage of.
 </p> 
-  <p>Committers: here's some JavaScript you might consider placing in a bookmark, courtesy of Doug Cutting. To use create a new bookmark and set the link url to</p> 
+  <p>Committers: here's some JavaScript you might consider placing in a bookmark, courtesy of Doug Cutting. To use create a new bookmark and set the link URL to</p> 
   <blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;"><code>javascript:void(location.href='https://s.apache.org/?action=create&amp;search=ON&amp;uri='+escape(location.href)) </code></blockquote>

content/blog/what_can_the_asf_buildbot.md

@@ -6,7 +6,7 @@ layout: post
 <p>The below information has just been published to the main&nbsp; ASF Buildbot URI <a href="http://ci.apache.org/buildbot.html" title="ASF Buildbot">ci.apache.org/buildbot.html</a>.</p><p>A summary of just some of the things the ASF Buildbot can do for your project:
 	</p><ul><li>Perform per commit build &amp; test runs for your project</li><li>Not just svn! - Buildbot can pull in from your Git/Mercurial branches too!</li><li>Build and Deploy your website to a staging area for review</li><li>Build and Deploy your website to mino (people) for syncing live</li><li>Automatically Build and Deploy Snapshots to Nexus staging area.</li><li>Create Nightly and historical zipped/tarred snapshot builds for download</li><li>Builds can be triggered manually from within your own freenode #IRC Channel</li><li>An IRCBot can report on success/failures of a build instantly</li><li>Build Success/Failures can go to your dev/notification mailing list</li><li>Perform multiple builds of an svn/git commit on multiple platforms asynchronously</li><li>ASF Buildbot uses the latest <a href="http://incubator.apache.org/rat" title="Incubating RAT project">RAT</a> build to check
 		for license header issues for all your files.
-		  </li><li>RAT Reports are published live instantly to ci.apache.org/$project/rat-report.[txt|html]</li><li>As indicated above, plain text or html versions of RAT reports are published.</li><li>[Coming Soon] - RAT Reports sent to your dev list, only new failures will be listed.</li><li>[Coming Soon] - Email a patch with inserted ASL 2.0 Headers into your failed files!!</li><li>Currently Buildbot has Ubuntu 8.04, 9.04 and Windows Server 2008 Slaves</li><li>[Coming Soon] - ASF Buildbot will soon have Solaris, FreeBSD 8 and Windows 7 Slaves</li></ul>
+		  </li><li>RAT Reports are published live instantly to ci.apache.org/$project/rat-report.[txt|html]</li><li>As indicated above, plain text or HTML versions of RAT reports are published.</li><li>[Coming Soon] - RAT Reports sent to your dev list, only new failures will be listed.</li><li>[Coming Soon] - Email a patch with inserted ASL 2.0 Headers into your failed files!!</li><li>Currently Buildbot has Ubuntu 8.04, 9.04 and Windows Server 2008 Slaves</li><li>[Coming Soon] - ASF Buildbot will soon have Solaris, FreeBSD 8 and Windows 7 Slaves</li></ul>
 
 	<p>Dont see a feature that you need? Join the <a href="mailto:[email protected]" title="Email Link to the builds subscribe list">builds.at.apache.org</a>
 	mailing list and request it now, or file a <a href="http://issues.apache.org/jira/browse/INFRA/component/12312782">Jira Ticket.</a></p>

content/pages/asf-pelican-build.md

@@ -54,7 +54,7 @@ PATH_METADATA = '(?P<path_no_ext>.*)\..*'
 ARTICLE_URL = ARTICLE_SAVE_AS = PAGE_URL = PAGE_SAVE_AS = '{path_no_ext}.html'
 # We want to serve our static files mixed with content
 STATIC_PATHS = ['.']
-# we want any html to be served as-is
+# we want any HTML to be served as-is
 READERS = {'html': None}
 # ignore README.md files in the content tree and the interviews and include folders
 IGNORE_FILES = ['README.md','interviews','include']
@@ -270,8 +270,8 @@ ASF-Pelican uses a version of <a href="https://github.com/github/cmark-gfm" targ
 - Many projects used the Apache CMS for their websites. Here are some differences from its `markdown.pl`.
 
   - [HTML Blocks][5]
-    - Make sure the first line of your html block starts in column one.
-    - A blank line terminates an html block
+    - Make sure the first line of your HTML block starts in column one.
+    - A blank line terminates an HTML block
       - [Exception][6] to this rule for `style`, `pre`, and `script`.
     - [Markdown content within an HTML block][7]
 

content/pages/asf-pelican-gettingstarted.md

@@ -91,5 +91,5 @@ Earlier versions of this template made use of a `pelicanconf.py` configuration f
    - `PLUGINS`
    - `ASF_DATA` - `asfdata.py` plugin settings
    - `ASF_GENID` - `asfgenid.py` plugin settings
-     `asfgenid.py` performs a series of html fixups including permalinks, heading ids, and table of contents
+     `asfgenid.py` performs a series of HTML fixups including permalinks, heading ids, and table of contents
 ```

content/pages/asf-pelican-plugins.md

@@ -64,7 +64,7 @@ ASF_GENID = {
 
 ## Readers (readers_init)
 
-The system sets two important readers at this point. Readers are responsible for transforming page files to html and
+The system sets two important readers at this point. Readers are responsible for transforming page files to HTML and
 providing a metadata dictionary.
 
 - GFMReader by the pelican-gfm plugin. This code is in a private repository - ask Infra. Transforms GitHub Flavored Markdown(GFM) to HTML.
@@ -80,7 +80,7 @@ providing a metadata dictionary.
 
 ## Content init (content_object_init)
 
-This is signaled after a reader has processed the site's content. At this point plugins can review, record, and transform the html content.
+This is signaled after a reader has processed the site's content. At this point plugins can review, record, and transform the HTML content.
 
 - The asfgenid plugin, `./asfgenid.py`, performs a number of steps. Some of the steps are optional.
   * Metadata transformation by looking up {{ key_expression }} in the page metadata.

content/pages/asf-pelican-theme.md

@@ -30,7 +30,7 @@ In this site the css included by `base.html` is in the `content` tree.
 There are site- or template-specific overrides to the stylesheet frameworks, but these are not done as Pelican specifies.
 
 - `styles.css` - consists of custom site CSS overrides. Edit as needed. Here we include the CSS for the ASF permalink style.
-  This file is in the same directory as the html and is included inline with `{% include "styles.css" %}`.
+  This file is in the same directory as the HTML and is included inline with `{% include "styles.css" %}`.
 
 ## Page metadata
 

content/pages/gfm.md

@@ -14,8 +14,8 @@ Sites built with the ASF-Pelican template use a version of [cmark-gfm][1] by [Gi
 - If your project previously built its site using the Apache CMS, here are some differences from `markdown.pl` that the CMS used:
 
   - [HTML Blocks][5]
-    - Make sure the first line of any html block starts in column one.
-    - A blank line terminates an html block
+    - Make sure the first line of any HTML block starts in column one.
+    - A blank line terminates an HTML block
       - [Exception][6] to this rule for `style`, `pre`, and `script`.
     - Review [Markdown content within an HTML block][7]
 
@@ -24,7 +24,7 @@ Sites built with the ASF-Pelican template use a version of [cmark-gfm][1] by [Gi
     - [url][10]
     - [email][11]
 
-  - [Disallowed html][12] the tagfilter extension disables certain html tags. The asfgenid plugin reenables `script`, `style`, and `iframe` html tags.
+  - [Disallowed html][12] the tagfilter extension disables certain HTML tags. The asfgenid plugin reenables `script`, `style`, and `iframe` HTML tags.
 
 - [Examples][13]