[PATCH 1/2] Fix typos in development guide.

[PATCH 1/2] Fix typos in development guide.

[Mikael Magnusson]

---
 Etc/zsh-development-guide |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/Etc/zsh-development-guide b/Etc/zsh-development-guide
index 77f0650..4c3f522 100644
--- a/Etc/zsh-development-guide
+++ b/Etc/zsh-development-guide
@@ -225,7 +225,7 @@ features.  Ensure you are familiar with the description of features under
 containing a list of all the features.  It should then return zero.
 It may return one to indicate features are not supported, but this is
 not recommended.  The function featuresarray conveniently interrogates
-the module's feature strctures for all standard features; space
+the module's feature structures for all standard features; space
 is left for abstract features at the end of the array and the names
 must be added by the module.  Note that heap memory should
 be used for this (zhalloc, etc.) as memory for the features array is not
@@ -258,7 +258,7 @@ particular they can be called before or after `boot_'.
 The function named `boot_' should register function wrappers, hooks and
 anything that will be visible to the user that is not handled by features_
 and enables_ (so features should not be turned on here).  It will be called
-after the `setup_'-function, and also after the intial set of features
+after the `setup_'-function, and also after the initial set of features
 have been set by calls to `features_' and `enables_'.

 The function named `cleanup_', is called when the user tries to unload
@@ -535,7 +535,7 @@ the `deleteparamdefs()' function described below.

 It is also possible to declare special parameters using
 the macro SPECIALPMDEF().  More care is required in this case.
-See, for example, many of the definitios in Src/Modules/parameter.c.
+See, for example, many of the definitions in Src/Modules/parameter.c.

 Math functions
 --------------
@@ -789,7 +789,7 @@ Documentation
       Saying `plugh' aloud doesn't have much effect, however.

   In this case, "zsh" is normal text (a name), "advent" is a command name
-  ocurring in the main text, "plugh" is a normal word that is being quoted
+  occurring in the main text, "plugh" is a normal word that is being quoted
   (it's the user that says `plugh', not the documentation), and "xyzzy"
   is some text to be typed literally that is being quoted.

-- 
1.6.0.2.GIT


--
Mikael Magnusson

[PATCH 2/2] Fix typos in completion style guide.

[Mikael Magnusson]

---
  Etc/completion-style-guide |    6 +++---
  1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/Etc/completion-style-guide b/Etc/completion-style-guide
index ec4efe2..b5de16f 100644
--- a/Etc/completion-style-guide
+++ b/Etc/completion-style-guide
@@ -8,7 +8,7 @@ to be distributed as part of zsh to maintain a level of consistency.
  Coding style:

  * Use two spaces for indentation and four for continuation lines except
-  where there are many continutation lines such as `_arguments' or
+  where there are many continuation lines such as `_arguments' or
    `_values' specs. Lines tend to be longer than in C code so less
    indentation makes sense.

@@ -46,7 +46,7 @@ where default values or units are indicated. Do not put them in
  per-match descriptions; they are better placed in the group
  descriptions. Put the units in parentheses after the description. So
  for example, do not use:
-  '--timeout[specifiy connection timeout in milliseconds]:timeout'
+  '--timeout[specify connection timeout in milliseconds]:timeout'
  but use:
    '--timeout[specify connection timeout]:timeout (ms)'

@@ -63,7 +63,7 @@ itsa meee, maaario

  Where two matches have identical meaning, give them the same
  description so that the completion system can group them together.
-Conventionally a brace exapansion of this form is used:
+Conventionally a brace expansion of this form is used:
    '(--context,-C)'{--context=,-C-}'[specify lines of context]:lines'
  You won't need the exclusion list if the option can be specified
  multiple times. It can also be useful to use the same description for
-- 
1.6.0.2.GIT


--
Mikael Magnusson

Re: [PATCH 2/2] Fix typos in completion style guide.

[Clint Adams]

On Sun, Oct 12, 2008 at 11:24:23AM +0200, Mikael Magnusson wrote:
> ---
>  Etc/completion-style-guide |    6 +++---
>  1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Etc/completion-style-guide b/Etc/completion-style-guide

This one broke because of wrapping.  Hand-applied; you can check what
I've missed this time below:

Index: Etc/completion-style-guide
===================================================================
RCS file: /cvsroot/zsh/zsh/Etc/completion-style-guide,v
retrieving revision 1.8
diff -u -r1.8 completion-style-guide
--- Etc/completion-style-guide	23 Jul 2003 11:06:59 -0000	1.8
+++ Etc/completion-style-guide	12 Oct 2008 10:58:14 -0000
@@ -8,7 +8,7 @@
 Coding style:
 
 * Use two spaces for indentation and four for continuation lines except
-  where there are many continutation lines such as `_arguments' or
+  where there are many continuation lines such as `_arguments' or
   `_values' specs. Lines tend to be longer than in C code so less
   indentation makes sense.
 
@@ -46,7 +46,7 @@
 per-match descriptions; they are better placed in the group
 descriptions. Put the units in parentheses after the description. So
 for example, do not use:
-  '--timeout[specifiy connection timeout in milliseconds]:timeout'
+  '--timeout[specify connection timeout in milliseconds]:timeout'
 but use:
   '--timeout[specify connection timeout]:timeout (ms)'
   
@@ -63,7 +63,7 @@
 
 Where two matches have identical meaning, give them the same
 description so that the completion system can group them together.
-Conventionally a brace exapansion of this form is used:
+Conventionally a brace expansion of this form is used:
   '(--context,-C)'{--context=,-C-}'[specify lines of context]:lines'
 You won't need the exclusion list if the option can be specified
 multiple times. It can also be useful to use the same description for

Re: [PATCH 2/2] Fix typos in completion style guide.

[Mikael Magnusson]

2008/10/12 Clint Adams <clint@zsh.org>:
> On Sun, Oct 12, 2008 at 11:24:23AM +0200, Mikael Magnusson wrote:
>> ---
>>  Etc/completion-style-guide |    6 +++---
>>  1 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/Etc/completion-style-guide b/Etc/completion-style-guide
>
> This one broke because of wrapping.  Hand-applied; you can check what
> I've missed this time below:

That's odd, I sent it in alpine which usually works fine... git rebase
tells me patch already applied, so everything is fine.

-- 
Mikael Magnusson