fix spelling (#148)

mr-c · web-flow · commit 49a46fa74ebd · 2022-09-21T17:05:42.000+02:00
diff --git a/content/EDITING.md b/content/EDITING.md
@@ -29,11 +29,11 @@ Instructions for editing specific pages and site components.
 <a id="navigation-menus"></a>
 ## Navigation Menus
 
-There are two nav menu templates currently available: 
+There are two nav menu templates currently available:
 
 * `_includes/top_nav.html` - the main site nav
   * Data: `_data/navigation.yml`
-  * Syles: `_sass/partials/_nav.scss`
+  * Styles: `_sass/partials/_nav.scss`
 * `_includes/left_nav.html` - left nav on an individual page
   * Data: `_data/navigation.yml` by default
     * Can also pull data from a page-specific file, e.g. `gallery.html` previously used `_data/user-gallery.yml` for its left nav
@@ -141,7 +141,7 @@ The first version will generate `<body class="body-page-short">`, and the second
 * `_includes/home/intro.html` - contains the intro paragraph and imports the video player
 * `_includes/home/features.html` - template for the "Features" boxes section. Relies on `_data/home.yml`
 * `_includes/home/users-mini-gallery.html` - the bottom gallery of logos. Relies on data in `_data/user-gallery.html`
-* `_includes/home/video-player.html` - template code for the video player ([Plyr](https://plyr.io/)). See [Video Player](#video-player) section for more info. 
+* `_includes/home/video-player.html` - template code for the video player ([Plyr](https://plyr.io/)). See [Video Player](#video-player) section for more info.
 
 <a id="features-boxes"></a>
 #### Features Boxes
@@ -293,7 +293,7 @@ Items containing special characters (colons, brackets, etc) may need to be wrapp
 <a id="foreign-languages"></a>
 ## Foreign Languages
 
-Text in foreign language should be entered in HTML and include the `lang` and `hreflang` attributes. Subtitles should include the `srclang` code Here's a list of [common language subtags](https://en.wikipedia.org/wiki/IETF_language_tag#List_of_subtags) You can also search via [the Language Subtag Lookup](https://r12a.github.io/app-subtags/) or check whether a tag is valid (e.g. `en-us` is valid, while `en_us` is not). 
+Text in foreign language should be entered in HTML and include the `lang` and `hreflang` attributes. Subtitles should include the `srclang` code Here's a list of [common language subtags](https://en.wikipedia.org/wiki/IETF_language_tag#List_of_subtags) You can also search via [the Language Subtag Lookup](https://r12a.github.io/app-subtags/) or check whether a tag is valid (e.g. `en-us` is valid, while `en_us` is not).
 
 Example usage:
 
@@ -303,7 +303,7 @@ Example usage:
 linked content is in Japanese -->
 <a href="https://github.com/pitagora-galaxy/cwl/wiki/CWL-Start-Guide-JP" lang="ja" hreflang="ja">
 
-<!-- Russian link doesn't have hreflang, since the linked 
+<!-- Russian link doesn't have hreflang, since the linked
 website auto-translates the content, based on the user's
 region -->
 <a href="https://stepik.org/course/1612/syllabus" lang="ru">
@@ -312,7 +312,7 @@ region -->
 <track src="{{ "/assets/video/subtitles/chinese_simplified.vtt" | relative_url }}" label="Chinese (Simplified)" kind="subtitles" srclang="zh-Hans">
 
 <!-- These can be mixed in with Markdown code -->
-* A series of <a href="https://stepik.org/lesson/35918/step/1?unit=15070"lang="ru" hreflang="ru"> is available 
+* A series of <a href="https://stepik.org/lesson/35918/step/1?unit=15070"lang="ru" hreflang="ru"> is available
 in Russian as part of the <a href="https://stepik.org/course/1612/syllabus" lang="ru">Управление вычислениями</a
 > (Computation Management) free online course.
 ```
@@ -324,7 +324,7 @@ Currently the site has some Japanese & Russian links. The corresponding codes ar
 
 For any markdown tables, prepend the following classes: `.table`, `.table-striped`, `.cols-2` or `.cols-3`:
 
-2 Column Table Example: 
+2 Column Table Example:
 
 ```markdown
 {: .table .table-striped .cols-2 }
@@ -343,14 +343,14 @@ For 3 column table, change `.cols-2` to `.cols-3`. i.e. `{: .table .table-stripe
 * Bootstrap 5.1.3
   * Site styles are built on top of Bootstrap 5.1.3
   * Nav menu relies on `/assets/js/bootstrap.min.js`
-* jQuery 3.5.1 
+* jQuery 3.5.1
   * Mobile Nav relies on this in `/assets/js/navCloseFix.js`, due to a bug where it wasn't closing properly
   * Back to the Top button relies on this
 
 <a id="bootstrap"></a>
 ### Bootstrap
 
-The site uses [Bootstrap 5](https://getbootstrap.com/docs/5.0/getting-started/introduction/) (specifically v5.0.0-beta3) for the base styles, and the nav menus. 
+The site uses [Bootstrap 5](https://getbootstrap.com/docs/5.0/getting-started/introduction/) (specifically v5.0.0-beta3) for the base styles, and the nav menus.
 
 Relevant folders & files:
 
@@ -362,7 +362,7 @@ The styles are loaded as the first import in `style.scss`. The JS code is loaded
 <a id="media-query-grid-breakpoints"></a>
 #### Media Query Grid Breakpoints
 
-Bootstrap grid breakpoints are originally found in ``_sass/bootstrap/_variables.scss`, and can be overriden in `_sass/partials/_variables.scss`
+Bootstrap grid breakpoints are originally found in ``_sass/bootstrap/_variables.scss`, and can be overridden in `_sass/partials/_variables.scss`
 
 The following breakpoints and max-widths are used for responsive design:
 
diff --git a/content/README.md b/content/README.md
@@ -1,6 +1,6 @@
 # CWL Website - Instructions
 
-Instructions on how to run and edit the main [commonwl.org](commonwl.org) website. 
+Instructions on how to run and edit the main [commonwl.org](commonwl.org) website.
 
 See the main [README.md](../README.md) for general [instructions](../README.md#contributing) on contributing. See the [Security Policy](https://github.com/common-workflow-language/cwl-website/security/policy) page to report a vulnerability.
 
@@ -54,7 +54,7 @@ It's important to specify both config files, in order. Otherwise Jekyll will gen
 
 **Use a custom url or port:** For convenience, you may wish to specify `--host cwl.test` and `--port 80` (or any other value), as follows: `bundle exec jekyll serve --config "_config.yml,_config_local.yml --host cwl.test --port 80`. **Note:** You may have to [update your hosts file](https://www.howtogeek.com/howto/27350/beginner-geek-how-to-edit-your-hosts-file/), in order for your computer to respect the custom url.
 
-**Command Line:** Anything you specify on the command line wil override the settings in your config files. For a full list of command line options, see Jekyll - Configuration Options [Serve Commands](https://jekyllrb.com/docs/configuration/options/#serve-command-options) and [Build Commands](https://jekyllrb.com/docs/configuration/options/#build-command-options)
+**Command Line:** Anything you specify on the command line will override the settings in your config files. For a full list of command line options, see Jekyll - Configuration Options [Serve Commands](https://jekyllrb.com/docs/configuration/options/#serve-command-options) and [Build Commands](https://jekyllrb.com/docs/configuration/options/#build-command-options)
 
 <a id="important-files-and-directories"></a>
 ### Important Files and Directories
diff --git a/content/features.md b/content/features.md
@@ -7,20 +7,30 @@ columns: 10
 
 ## Benefits of Workflows and Standards
 
-### Why Use Workfows?
+### Why Use Workflows?
 
 Workflows and using workflow tools help make your computation methods portable, maintainable, reproducible and shareable. Often analysis methods contain many steps, perhaps in multiple languages and workflows help researchers document, run and maintain these complicated analyses.
 Using a workflow system rather than a series of scripts has a number of benefits including abstraction, scaling, automation, and provenance (ASAP).
 Workflows enable a clear abstraction about the components of your analysis, the relationship between the components and the inputs and outputs for each component allows for a well-labeled analysis with documented expectation. This abstraction helps enable the other benefits of scaling, automation and provenance.
 Workflow execution can be parallelized or distributed making use of cluster, cloud, and high performance computing (HPC) environments. This helps to solve larger problems and analyze larger datasets faster.
 
-Automation helps when running repetitive pipelines for example when running parameter sweeps or the same analysis on different sets of data. Workflow engines can use the inherient abstraction of workflows to efficently track, plan and manage the executation of workflow components.
-Lastly, provenance tracking helps with auditing, tranparency, and validation. Ultimately, using workflows in the long run helps save time and effort and allows for easier scaling, tracking, sharing and reuse.
+Automation helps when running repetitive pipelines, for example when running
+parameter sweeps or the same analysis on different sets of data. Workflow engines
+can use the inherient abstraction of workflows to efficiently track, plan and
+manage the execution of workflow components.
+Lastly, provenance tracking helps with auditing, tranparency, and validation.
+Ultimately, using workflows in the long run helps save time and effort and
+allows for easier scaling, tracking, sharing and reuse.
 
 ### Why Use a Standard?
 
-A standard for sharing and reusing workflows can provide a solution to describing portable,re-usable workflows while also being workflow-engine and vendor-neutral.
-Although workflows are [very popular](https://s.apache.org/existing-workflow-systems), prior to the CWL standards every workflow system was incompatible with every other. This means, those users not using the CWL standards are required to express their computational workflows in a different way everytime they have to use another workflow system. This greatly hampers reuse and collaboration.
+A standard for sharing and reusing workflows can provide a solution to describing
+portable,re-usable workflows while also being workflow-engine and vendor-neutral.
+Although workflows are [very popular](https://s.apache.org/existing-workflow-systems),
+prior to the CWL standards every workflow system was incompatible with every other.
+This means, those users not using the CWL standards are required to express their
+computational workflows in a different way every time they have to use another
+workflow system. This greatly hampers reuse and collaboration.
 
 ### When to Use CWL?
 
@@ -29,7 +39,7 @@ command-line tool based data analysis.
 CWL is for dataflow style batch analysis consisting of command line programs. It is not designed for supporting safe interaction with stateful (web) services, real-time communication between workflow steps, or workflows that need particular steps run at or during a
 specific day/time-frame.
 
-## Reusability and Reproduciblity with CWL
+## Reusability and Reproducibility with CWL
 CWL workflows are portable, reusable, and flexible.  Reproduction, reuse, and replication of computational methods requires a complete description of what computer applications were used, how exactly they were used, and how they were connected to each other. To this end, CWL enables portability by being explicit about inputs/outputs to form the data flow, data locations and execution models. CWL supports using software container technologies, such as Docker and Singularity, to enable portability. For increased flexiblity, individual CWL tool definitions can be reused in any new workflow.
 
 <figure>
@@ -42,7 +52,10 @@ Benefits of CWL including flexibility, portability, and scalability. CWL is well
 
 ## Parallelization and Scale with CWL
 
-CWL workflows describe each step with explict inputs and outputs.  Workflow steps in CWL are not necessarily run in the order they are listed, instead the order is determined by the dependencies between steps. Workflow steps which do not depend on one another may run in parallel.
+CWL workflows describe each step with explicit inputs and outputs.  Workflow steps
+in CWL are not necessarily run in the order they are listed, instead the order
+is determined by the dependencies between steps. Workflow steps which do not
+depend on one another may run in parallel.
 
 Additionally, the **[scatter](https://www.commonwl.org/user_guide/23-scatter-workflow/index.html)** feature in CWL allows the repeated execution of a CWL step in parallel (depending on the resources available) over a list of inputs.  This can be done without requiring the modification of the underlying tool description.
 
diff --git a/content/getting-started.html b/content/getting-started.html
@@ -12,10 +12,10 @@
 
 * Learn to write CWL using the [CWL user guide](/user_guide/) which provides a gentle introduction to creating CWL command line tool and workflow descriptions.
 * Browse [CWL Implementations](/implementations/) to find a software package that's right for you.
-* Follow [CWL Recommended Practices](http://www.commonwl.org/user_guide/rec-practices/) to make your CWL tools and workflows more efficent, reusable and transparent.
+* Follow [CWL Recommended Practices](http://www.commonwl.org/user_guide/rec-practices/) to make your CWL tools and workflows more efficient, reusable and transparent.
 * Read <a href="https://github.com/pitagora-galaxy/cwl/wiki/CWL-Start-Guide-JP" lang="ja" hreflang="ja">CWLの日本語での解説ドキュメント</a>  a 15 minute introduction to the CWL project in Japanese.
 * Watch a series of [video lessons about CWL](https://stepik.org/lesson/35918/step/1?unit=15070) in Russian as part of the <a href="https://stepik.org/course/1612/syllabus" lang="ru">Управление вычислениями</a> (Computation Management) free online course.
-* Find [CWL descriptions for life-science tools](https://github.com/common-workflow-library/bio-cwl-tools) to use directly or incoporate into your workflows.
+* Find [CWL descriptions for life-science tools](https://github.com/common-workflow-library/bio-cwl-tools) to use directly or incorporate into your workflows.
 
 {%- endcapture -%}
 
diff --git a/content/implementations.md b/content/implementations.md
@@ -23,7 +23,7 @@ workflows and they are available from vendors such as Curii
 Wide adoption benefits from our principles: CWL offers
 conformance tests, but the CWL community does not yet test or certify
 CWL implementations, or specific technology stacks. Instead,
-plaform/service providers self-certify support for CWL, based on a
+platform/service providers self-certify support for CWL, based on a
 particular technology configuration they deploy and maintain.
 
 {:.cwl-red}
