Fix numerous typos found with ispell

Author: zbeekman

CHANGELOG.md

@@ -48,10 +48,10 @@
 
 **Fixed issues:**
 
-- Fixed innacurate coverage reports via
+- Fixed inaccurate coverage reports via
   [PR \#109](https://github.com/jacobwilliams/json-fortran/pull/109)
   from [zbeekman](https://github.com/zbeekman)
-- Fixed a small consistency issue when outputing floating point
+- Fixed a small consistency issue when outputting floating point
   numbers via
   [PR \#125](https://github.com/jacobwilliams/json-fortran/pull/125)
 - Problems writing JSON to `error_unit` (0) due to JSON-Fortran's
@@ -118,7 +118,7 @@ or [Download v4.1.0](https://github.com/jacobwilliams/json-fortran/releases/tag/
 
 **Enhancements:**
 
-- Runtime speed improvements
+- Run-time speed improvements
   [\#75](https://github.com/jacobwilliams/json-fortran/issues/75)
   implemented in
   [PR \#93](https://github.com/jacobwilliams/json-fortran/pull/93)
@@ -180,7 +180,7 @@ or [Download v4.0.0](https://github.com/jacobwilliams/json-fortran/releases/tag/
 - Discrepancy with dummy argument attributes for
   path between `get` and `get_..._vec` procedures
   [\#79](https://github.com/jacobwilliams/json-fortran/issues/79)
-- Small bugfix for [CMake](http://www.cmake.org) install
+- Small bug fix for [CMake](http://www.cmake.org) install
   [\#68](https://github.com/jacobwilliams/json-fortran/pull/68)
   ([zbeekman](https://github.com/zbeekman))
 - JSON output files from tests are overwriting expected outputs and
@@ -220,7 +220,7 @@ or [Download v3.1.0](https://github.com/jacobwilliams/json-fortran/releases/tag/
   from [jacobwilliams](https://github.com/jacobwilliams))
 - Read JSON structure from a character string
   [\#5](https://github.com/jacobwilliams/json-fortran/issues/5)
-- Adopeted official contributing guidelines and added a
+- Adopted official contributing guidelines and added a
   `CONTRIBUTING.md`
   [\#47](https://github.com/jacobwilliams/json-fortran/issues/47)
 
@@ -231,11 +231,11 @@ or [Download v3.1.0](https://github.com/jacobwilliams/json-fortran/releases/tag/
   fixed by
   [PR \#54](https://github.com/jacobwilliams/json-fortran/pull/54)
   (from [zbeekman](https://github.com/zbeekman))
-- Segfaults and unexpexted behavior due to optional dummy arguments
+- Segfaults and unexpected behavior due to optional dummy arguments
   being dereferenced outside of `if (present(…))`
   [\#52](https://github.com/jacobwilliams/json-fortran/issues/52)
 - Documentation not being produced for tests because tests directory
-  should be subdirectory of src
+  should be sub-directory of src
   [\#49](https://github.com/jacobwilliams/json-fortran/issues/49)
 - Example 8 failing on gfortran 4.9.2
   [\#44](https://github.com/jacobwilliams/json-fortran/issues/44)
@@ -317,7 +317,7 @@ or [Download v2.0.0](https://github.com/jacobwilliams/json-fortran/releases/tag/
 
 **Enhancements:**
 - Significant changes to the API including new procedures
-- Code refactoring
+- Code re-factoring
 - SCons build added thanks to [@bruceravel](https://github.com/bruceravel)
 
 **Fixed issues:**
@@ -365,15 +365,15 @@ or [Download v2.0.0](https://github.com/jacobwilliams/json-fortran/releases/tag/
   [ROBODoc](https://github.com/gumpu/ROBODoc) must be specified in
   CMakeLists.txt manually
   [\#17](https://github.com/jacobwilliams/json-fortran/issues/17)
-- Invalid json input files (`test1.json`, `test5.json`)
+- Invalid JSON input files (`test1.json`, `test5.json`)
   [\#10](https://github.com/jacobwilliams/json-fortran/issues/10),
   fixed by
   [PR \#11](https://github.com/jacobwilliams/json-fortran/pull/11)
   ([zbeekman](https://github.com/zbeekman))
 - `char()` is processor dependent, use `achar()`
   [\#20](https://github.com/jacobwilliams/json-fortran/pull/20)
   (pull request from [zbeekman](https://github.com/zbeekman))
-- Bugfix for [ROBODoc](https://github.com/gumpu/ROBODoc) documentation
+- Bug-fix for [ROBODoc](https://github.com/gumpu/ROBODoc) documentation
   generation with [CMake](http://www.cmake.org)
   [\#16](https://github.com/jacobwilliams/json-fortran/pull/16)
   (pull request from [zbeekman](https://github.com/zbeekman))

CONTRIBUTING.md

@@ -1,6 +1,6 @@
-# Contributing to [json-fortran](README.md)
+# Contributing to JSON-Fortran
 
-Looking to contribute something to [json-fortran](https://github.com/jacobwilliams/json-fortran)? **Here's how you can help.**
+Looking to contribute something to [JSON-Fortran](https://github.com/jacobwilliams/json-fortran)? **Here's how you can help.**
 
 <!-- markdown-toc start - Don't edit this section. Run M-x markdown-toc/generate-toc again -->
 **Table of Contents**
@@ -20,7 +20,7 @@ Looking to contribute something to [json-fortran](https://github.com/jacobwillia
 [top](#contributing-to-json-fortran)
 ## Filing issues
 
-- Before filing a new [issue](https://github.com/jacobwilliams/json-fortran/issues), please perform a search to see if that issue has already been filed by someone else, and whether or not a solution exists. If you are experiencing the same issue as one that's already posted, please leave any additional comments and information under the existing issue. If your issue is related to a previous issue, but substantively different, file a new issue and include a mention of the related issue in text, using GitHub's `#<issue-number>` syntax.
+- Before filing a new [issue](https://github.com/jacobwilliams/json-fortran/issues), please perform a search to see if that issue has already been filed by someone else, and whether or not a solution exists. If you are experiencing the same issue as one that's already posted, please leave any additional comments and information under the existing issue. If your issue is related to a previous issue, but substantively different, file a new issue and include a mention of the related issue in text, using Jib's `#<issue-number>` syntax.
 - When filing an issue please try to include all of the following information
   1. Problem description: What behavior are you seeing that you think is erroneous
   1. Installation method: Did you build the code with one of the included build scripts? Some other way? Install from a binary package?
@@ -53,7 +53,7 @@ Looking to contribute something to [json-fortran](https://github.com/jacobwillia
 - Pull requests should address one issue at a time, and each commit should be a set of self contained, related changes. If you forget something in a commit, please use `git rebase -i <ref>^` to amend and/or squash erroneous commits. Here `<ref>` is the reference to to oldest commit needing to be modified (SHA, or `HEAD~4`, etc.)
 - Each commit should compile, and ideally pass the tests. Very complicated new features or fixes, may have commits that don't pass tests, if otherwise the commit history would include far to many changes in any given commit. Use an interactive rebase to fix any of these issues, as described above.
 - Each commit should have a concise, descriptive message following the
-  guidlines laid out
+  guidelines laid out
   [here](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
 - Make sure to document your changes in the
   [CHANGELOG](https://github.com/jacobwilliams/json-fortran/blob/master/CHANGELOG.md)
@@ -73,7 +73,7 @@ git rebase upstream/master
 - Create a branch in your fork with a descriptive name that also includes the [issue number](https://github.com/jacobwilliams/json-fortran/issues), if applicable. For example, after forking the repo, you can run something like `git checkout -b Unicode-support-issue-35` before starting work on [issue #35 : Unicode support](https://github.com/jacobwilliams/json-fortran/issues/35)
 - When you're content with your changes, your commits are clean, self contained, with concise descriptive messages, and your changes compile and pass the tests, submit a pull request. We will review your changes, and may ask for certain modifications to be made.
 - Pull requests are tested by our [travis-ci](https://travis-ci.org/jacobwilliams/json-fortran) continuous integration system, and any errors uncovered will need to be fixed before the pull request can be merged into master.
-- The json-fortran library and associated documentation is released under a BSD style [license](https://github.com/jacobwilliams/json-fortran/blob/master/LICENSE).  By submitting a pull request, you are agreeing to release your code under the same license.  Note that code with GPL or other "copyleft" style licenses will not be accepted.
+- The JSON-Fortran library and associated documentation is released under a BSD style [license](https://github.com/jacobwilliams/json-fortran/blob/master/LICENSE).  By submitting a pull request, you are agreeing to release your code under the same license.  Note that code with GPL or other "copyleft" style licenses will not be accepted.
 
 [top](#contributing-to-json-fortran)
 ## Coding Standards
@@ -87,7 +87,7 @@ git rebase upstream/master
 - New tests are added to the `src/tests` directory and are named
   `jf_test_<#>.[Ff]90`. Each test is a stand alone Fortran program
   which will automatically be compiled and linked against the
-  json-fortran library so long as it follows this naming
+  JSON-Fortran library so long as it follows this naming
   convention. If any of the tests fail, the test program should exit
   with a non-zero return status, using the `stop 2` intrinsic
   statement. (The Fortran standard does not require the 'processor' to
@@ -99,6 +99,6 @@ git rebase upstream/master
 - *Do NOT* allow your editor to make a bunch of indentation or white space changes, that will introduce non-substantive changes on lines that you have not actually edited.
 - The coding style is modern free-form Fortran, consistent with the Fortran 2008 standard.  Note that the two supported compilers (ifort and gfortran) do not currently include the entire Fortran 2008 standard. Therefore, only those language features supported by Gfortran 4.9 and Intel 13.1.0 are currently allowed.  This also means that previous versions of these compilers are not supported, and major changes to the code to support earlier compilers (or Fortran 95) will not be accepted.  At some point in the future (when compiler support has improved), all Fortran 2008 features will be allowed.
 - All subroutines and functions *must* be properly documented.  This includes useful inline comments as well as comment blocks using the [FORD](https://github.com/cmacmackin/ford/wiki/Writing-Documentation) syntax.
-- For simplicity, json-fortran currently consists of one module file. It is not envisioned that it will ever need to expand to include multiple files (if it does, there would need to be a very good reason).
+- For simplicity, JSON-Fortran currently consists of one module file. It is not envisioned that it will ever need to expand to include multiple files (if it does, there would need to be a very good reason).
 
 [top](#contributing-to-json-fortran)

README.md

@@ -1,4 +1,4 @@
-json-fortran
+JSON-Fortran
 ============
 
 [![GitHub release](https://img.shields.io/github/release/jacobwilliams/json-fortran.svg?style=plastic)](https://github.com/jacobwilliams/json-fortran/releases/latest)
@@ -7,12 +7,12 @@ A Fortran 2008 JSON API
 <!-- markdown-toc start - Don't edit this section. Run M-x markdown-toc/generate-toc again -->
 **Table of Contents**
 
-- [json-fortran](#json-fortran)
+- [JSON-Fortran](#json-fortran)
     - [Status](#status)
     - [Brief description](#brief-description)
     - [Download](#download)
     - [Building the library](#building-the-library)
-    - [Exapmle Usage](#exapmle-usage)
+    - [Example Usage](#example-usage)
         - [Reading JSON from a file](#reading-json-from-a-file)
         - [Reading JSON from a string](#reading-json-from-a-string)
         - [Modifying variables in a JSON file](#modifying-variables-in-a-json-file)
@@ -135,7 +135,7 @@ endforeach()
 
 [top](#json-fortran)
 
-Exapmle Usage
+Example Usage
 ---------------
 In this section the basic functionality of the JSON-Fortran library is illustrated.
 

pages/development-resources/index.md

@@ -5,11 +5,14 @@ JSON-Fortran contributors and developers.
 
 # Contributing
 
-The guidlines for contributing to JSON-Fortran can be found
+The guidelines for contributing to JSON-Fortran can be found
 [here](CONTRIBUTING.html). Please read these before posting
 [issues](https://github.com/jacobwilliams/json-fortran/issues)
 or opening
-[pull requests](https://github.com/jacobwilliams/json-fortran/pulls).
+[pull requests](https://github.com/jacobwilliams/json-fortran/pulls). Also,
+please carefully read the
+[LICENSE](|url|/page/development-resources/LICENSE.html) before using
+JSON-Fortran in an application, or contributing code.
 
 
 # Test Coverage Information
@@ -21,3 +24,20 @@ automatically generated by
 [FoBiS.py](https://github.com/szaghi/FoBiS). If all procedures are
 listed as covered, then please take a look at the
 [Codecov.io coverage suggestions](https://codecov.io/github/jacobwilliams/json-fortran/features/suggestions?ref=master).
+
+# Scripts
+
+Scripts used to build and test JSON-Fortran. This is a partial list of
+scripts used in building and testing JSON-Fortran, as well as
+deploying documentation and managing test coverage information.
+
+- [`build.sh`](build.sh.html)
+- [`.travis.yml`](travis.yml.html)
+- [`deploy.sh`](deploy.sh.html)
+- [`gccr.pl`](gccr.pl.html)
+
+# Release Checklist
+
+[This](|url|/page/development-resources/release-checklist.html) is a
+checklist of tasks to be performed when tagging a new release of
+JSON-Fortran. The current stable version is **{!__VERSION__!}**.

pages/development-resources/release-checklist.md

@@ -2,16 +2,16 @@ title: Release Checklist
 
 When tagging a new release please follow this checklist so that the
 documentation will be updated correctly, and version strings will
-remain accuracte.
+remain accurate.
 
 # Release Checklist
 
  1. Make sure you are working from the master branch: `git checkout master`
  1. Update the `CHANGELOG.md`
 	 1. Ensure that the changes listed under
-        [Unreleased](|url|/page/releases/index.html#Unreleased) are up
+        [Unreleased](|url|/page/releases/index.html#unreleased) are up
         to date and accurate.
-	     1. Look at the latest [changes commited to GitHub since the
+	     1. Look at the latest [changes committed to GitHub since the
             last release](https://github.com/jacobwilliams/json-fortran/compare/{!__VERSION__!}...HEAD),
             {!__VERSION__!}. This will only be accurate if you have
             not yet updated `__VERSION__`. If you *have* updated
@@ -20,11 +20,11 @@ remain accuracte.
 		 1. Run the
             [`github_changelog_generator`](https://github.com/skywinder/github-changelog-generator)
             as follows, and compare the output to the
-            [Unreleased](|url|/page/releases/index.html#Unreleased)
+            [unreleased](|url|/page/releases/index.html#unreleased)
             section of the `CHANGELOG.md`:
 			`github_changelog_generator -o Unreleased.md
             --unreleased-only --bugs-label "**Fixed issues:**"
-            --enhancement-lable "**Enhancements:**" --issues-lable
+            --enhancement-label "**Enhancements:**" --issues-label
             "**Fixed issues:**"` and make sure that you have a
             16-digit GitHub token stored in the environment variable
             `CHANGELOG_GITHUB_TOKEN`. Compare generated
@@ -47,7 +47,7 @@ remain accuracte.
  1. Add an entry in `pages/releases/index.md` under the "Past
     Releases" heading
      1. Copy/paste the most recent one listed and replace all
-        occurences of the old version string with the new version
+        occurrences of the old version string with the new version
         string
 	 1. Add `pages/releases/index.md` to the git index: `git add pages/releases/index.md`
  1. Update the version string in remaining files requiring manual edits:
@@ -57,8 +57,8 @@ remain accuracte.
      README.md`
  1. Commit the changes to the master branch: `git commit`
  1. Create the tag: `git tag <new version>`
- 1. [deploy.sh](|url|/page/development-resources/deploy.sh.html) will
-    publish the documentation for the latest tag from
+ 1. [deploy.sh](deploy.sh.html) will publish the documentation for the
+    latest tag from
     [Travis-CI](https://travis-ci.org/jacobwilliams/json-fortran) to
     https://jacobwilliams.github.io/json-fortran/<version>/ if all
     goes according to plan
@@ -74,7 +74,7 @@ remain accuracte.
 	 1. Add your fork as a pushable remote: `git remote add
         YOUR_USERNAME https://github.com/YOUR_USERNAME/homebrew.git`
 	 1. Make sure you're on the master branch: `git checkout master`
-	 1. Make sure eveything is up to date: `brew update` (this calls
+	 1. Make sure everything is up to date: `brew update` (this calls
         `git pull`)
 	 1. Create a new branch from the latest master branch with `git
         checkout -b YOUR_BRANCH_NAME origin/master`
@@ -84,7 +84,7 @@ remain accuracte.
         checksum at the top of the formula. These should be changed to
         correspond to the new version of the compressed tarball
         available on newly minted
-        [latest releaase page](https://github.com/jacobwilliams/json-fortran/releases/latest)
+        [latest release page](https://github.com/jacobwilliams/json-fortran/releases/latest)
 	 1. Test the changes to make sure that they will be accepted:
          1. `brew audit --strict --online json-fortran`
 		 1. `brew rm json-fortran`

pages/development-resources/travis.yml.md

@@ -5,6 +5,6 @@ This is the
 used to perform continuous integration testing for JSON-Fortran, and
 trigger automatic documentation deployment.
 
-```YAML
+```yml
 {!.travis.yml!}
 ```

pages/index.md

@@ -6,17 +6,17 @@ title: Additional Documentation
 
 # Past Releases
 
-Docementation for official, tagged releases can be found
+Documentation for official, tagged releases can be found
 [here](releases/index.html), including the changelog, and download links.
 
-# DeveLopment Documentation
+# Development Documentation
 
 Additional documentation useful to JSON-Fortran contributors can be
-found [here](development-resources/index.html), including contributing guidlines
+found [here](development-resources/index.html), including contributing guidelines
 and test coverage reports.
 
 # General Documentation
 
 A [README](README.html), the same one that's posted on
-[Github](https://github.com/jacobwilliams/json-fortran), can be found
+[GitHub](https://github.com/jacobwilliams/json-fortran), can be found
 [here](README.html).