Skip to content

README: Typos fixed #558

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 7, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -164,7 +164,7 @@ The easiest way to use cwltool to run a tool or workflow from Python is to use a
Leveraging SoftwareRequirements (Beta)
--------------------------------------

CWL tools may be decoarated with ``SoftwareRequirement`` hints that cwltool
CWL tools may be decorated with ``SoftwareRequirement`` hints that cwltool
may in turn use to resolve to packages in various package managers or
dependency management systems such as `Environment Modules
<http://modules.sourceforge.net/>`__.
Expand Down Expand Up @@ -193,8 +193,8 @@ following ``hint`` definition for an example CWL tool.
- r93

Now imagine deploying cwltool on a cluster with Software Modules installed
and that a ``seqtk`` module is avaialble at version ``r93``. This means cluster
users likely won't have the ``seqtk`` the binary on their ``PATH`` by default but after
and that a ``seqtk`` module is available at version ``r93``. This means cluster
users likely won't have the binary ``seqtk`` on their ``PATH`` by default, but after
sourcing this module with the command ``modulecmd sh load seqtk/r93`` ``seqtk`` is
available on the ``PATH``. A simple dependency resolvers configuration file, called
``dependency-resolvers-conf.yml`` for instance, that would enable cwltool to source
Expand Down