Skip to content

Commit 56b4bde

Browse files
committed
fix some readme typos
1 parent a72a458 commit 56b4bde

File tree

2 files changed

+10
-9
lines changed

2 files changed

+10
-9
lines changed

README.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -22,10 +22,10 @@ Create beautiful bash scripts from simple YAML configuration
2222
- [Prerequisites](#prerequisites)
2323
- [What is Bashly](#what-is-bashly)
2424
- [Usage](#usage)
25-
- [Using the input arguemnts in your code](#using-the-input-arguemnts-in-your-code)
25+
- [Using the input arguments in your code](#using-the-input-arguments-in-your-code)
2626
- [Examples](#examples)
27-
- [Sample configuraiton for a script without commands](#sample-configuraiton-for-a-script-without-commands)
28-
- [Sample configuraiton for a script with commands](#sample-configuraiton-for-a-script-with-commands)
27+
- [Sample configuration for a script without commands](#sample-configuration-for-a-script-without-commands)
28+
- [Sample configuration for a script with commands](#sample-configuration-for-a-script-with-commands)
2929
- [Configuration Reference](#configuration-reference)
3030
- [Command options](#command-options)
3131
- [Argument options](#argument-options)
@@ -113,7 +113,7 @@ Finally, edit the files in the `src` folder. Each of your script's commands
113113
get their own file. Once you edit, run `bashly generate` again to merge the
114114
content from your functions back into the script.
115115

116-
### Using the input arguemnts in your code
116+
### Using the input arguments in your code
117117

118118
In order to access the parsed arguments in any of your partial scripts, you
119119
may simply access the `$args` associative array.
@@ -163,13 +163,13 @@ This is detected automatically by the contents of the configuration: If it
163163
contains a `commands` definition, it will generate a script with commands.
164164

165165

166-
### Sample configuraiton for a script without commands
166+
### Sample configuration for a script without commands
167167

168168
- Generate this script by running `bashly generate --minimal`
169169
- [See the initial sample bashly.yml file](examples/minimal/src/bashly.yml)
170170
- [See the generated bash script](examples/minimal/download)
171171

172-
### Sample configuraiton for a script with commands
172+
### Sample configuration for a script with commands
173173

174174
- Generate this script by running `bashly generate`
175175
- [See the initial sample bashly.yml file](examples/commands/src/bashly.yml)
@@ -193,7 +193,7 @@ The `bashly.yml` configuration file consists of these types:
193193

194194
### Command options
195195

196-
Unless otherwise specified, these definitiona can be used for both the root
196+
Unless otherwise specified, these definitions can be used for both the root
197197
command and subcommands (under the `commands` definition).
198198

199199
Option | Description
@@ -274,9 +274,9 @@ set.
274274
If you experience any issue, have a question or a suggestion, or if you wish
275275
to contribute, feel free to [open an issue][issues].
276276

277+
278+
277279
[issues]: https://github.com/DannyBen/bashly/issues
278280
[rush]: https://github.com/DannyBen/rush-cli
279281
[alf]: https://github.com/DannyBen/alf
280282
[git-changelog]: https://github.com/DannyBen/git-changelog
281-
282-

lib/bashly/models/command.rb

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,7 @@ def catch_all_label
4141
end
4242
end
4343

44+
# Returns a used defined help string for the catch_all directive
4445
def catch_all_help
4546
return nil unless catch_all
4647

0 commit comments

Comments
 (0)