Skip to content

Commit b2b47f9

Browse files
authored
README: Typos fixed
1 parent 1f2dbf0 commit b2b47f9

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -164,7 +164,7 @@ The easiest way to use cwltool to run a tool or workflow from Python is to use a
164164
Leveraging SoftwareRequirements (Beta)
165165
--------------------------------------
166166

167-
CWL tools may be decoarated with ``SoftwareRequirement`` hints that cwltool
167+
CWL tools may be decorated with ``SoftwareRequirement`` hints that cwltool
168168
may in turn use to resolve to packages in various package managers or
169169
dependency management systems such as `Environment Modules
170170
<http://modules.sourceforge.net/>`__.
@@ -193,8 +193,8 @@ following ``hint`` definition for an example CWL tool.
193193
- r93
194194
195195
Now imagine deploying cwltool on a cluster with Software Modules installed
196-
and that a ``seqtk`` module is avaialble at version ``r93``. This means cluster
197-
users likely won't have the ``seqtk`` the binary on their ``PATH`` by default but after
196+
and that a ``seqtk`` module is available at version ``r93``. This means cluster
197+
users likely won't have the binary ``seqtk`` on their ``PATH`` by default, but after
198198
sourcing this module with the command ``modulecmd sh load seqtk/r93`` ``seqtk`` is
199199
available on the ``PATH``. A simple dependency resolvers configuration file, called
200200
``dependency-resolvers-conf.yml`` for instance, that would enable cwltool to source

0 commit comments

Comments
 (0)