From 8303f7626e61d6aeadc5ccf04bda12474acb6cd5 Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Sun, 13 Oct 2013 16:26:12 -0400 Subject: spell check --- public/bash-arrays.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'public/bash-arrays.md') diff --git a/public/bash-arrays.md b/public/bash-arrays.md index 480d168..e78b8d5 100644 --- a/public/bash-arrays.md +++ b/public/bash-arrays.md @@ -7,7 +7,7 @@ that if you need arrays, you shouldn't be using Bash. If we reject the notion that one should never use Bash for scripting, then thinking you don't need Bash arrays is what I like to call "wrong". -The simple expanation of why everybody who programs in Bash needs to +The simple explanation of why everybody who programs in Bash needs to understand arrays is this: command line arguments are exposed as an array. Does your script take any arguments on the command line? Great, you need to work with an array! @@ -53,7 +53,7 @@ difference between `@` and `*`. "${array[*]}" Returns every element of the array in a single - whitepace-separated string. + whitespace-separated string. @@ -153,7 +153,7 @@ with letters and underscore), that *mostly* match up with the normal array syntax. Setting the arguments array, on the other hand, is pretty different. -That's fine, because setting the arguments array is less usefull +That's fine, because setting the arguments array is less useful anyway. -- cgit v1.2.3