[Zope3-checkins] SVN: Zope3/trunk/src/zope/ Typo fixes.

[Marius Gedminas]

Log message for revision 41757:
  Typo fixes.
  
  

Changed:
  U   Zope3/trunk/src/zope/formlib/form.txt
  U   Zope3/trunk/src/zope/testbrowser/README.txt

-=-
Modified: Zope3/trunk/src/zope/formlib/form.txt
===================================================================
--- Zope3/trunk/src/zope/formlib/form.txt	2006-02-22 20:17:54 UTC (rev 41756)
+++ Zope3/trunk/src/zope/formlib/form.txt	2006-02-23 13:49:34 UTC (rev 41757)
@@ -12,15 +12,15 @@
 templates in practice.
 
 This document starts with low-level APIs.  We eventually build up to
-higherlevel APIs that allow forms to be defined with just a little bit
-of meta data.  Impatiant readers may wish to skip to the later
+higher-level APIs that allow forms to be defined with just a little bit
+of meta data.  Impatient readers may wish to skip to the later
 sections, especially the section on `Helpful base classes`_. :)
 
 A form class can define ordered collections of "form fields" using
 the `Fields` constructor. Form fields are distinct from and build on
 schema fields.  A schema field specified attribute values.  Form
 fields specify how a schema field should be used in a form.  The
-simplest way to define a collection onf form fields is by passing a
+simplest way to define a collection of form fields is by passing a
 schema to the `Fields` constructor:
 
     >>> from zope import interface, schema
@@ -53,7 +53,7 @@
     >>> [w.__name__ for w in MyForm.form_fields.select('name', 'identifier')]
     ['name', 'identifier']
 
-or by omiting fields:
+or by omitting fields:
 
     >>> [w.__name__ for w in MyForm.form_fields.omit('now', 'identifier')]
     ['name', 'min_size', 'max_size']
@@ -654,7 +654,7 @@
   - `status` is a string that, if set, is displayed at the top of the
     form.
 
-  - `errors` is the set of errors found when valiadting.
+  - `errors` is the set of errors found when validating.
 
   - `widgets` is a list of set-up widgets
 
@@ -850,7 +850,7 @@
 Helpful base classes
 ====================
 
-Our form has a lot of repetative code. A number of helpful base
+Our form has a lot of repetitive code. A number of helpful base
 classes provide standard form implementation.
 
 Form
@@ -869,7 +869,7 @@
   To render the form
 
 `template`
-  A default template.  Note that this a NamedTemplate named "default",
+  A default template.  Note that this is a NamedTemplate named "default",
   so the template may also be overridden by registering an alternate
   default template.
 
@@ -929,7 +929,7 @@
 
 We also used the `action` decorator.  The action decorator:
 
-- creates an `actions` variable if one isn't aleady created,
+- creates an `actions` variable if one isn't already created,
 
 - defines an action with the given label and any other arguments, and
 
@@ -1204,7 +1204,7 @@
 ========================
 
 The form-field constructor is very flexible.  We've already seen that
-we can sppply multiple schemas.  Here are some other things you can
+we can supply multiple schemas.  Here are some other things you can
 do.
 
 Specifying individual fields
@@ -1242,11 +1242,11 @@
 
 But make sure the fields have a '__name__', as was done above.
 
-Concatinating field collections
+Concatenating field collections
 -------------------------------
 
 It is sometimes convenient to combine multiple field collections.
-Field collections support concatination. For example, we may want to
+Field collections support concatenation. For example, we may want to
 combine field definitions:
 
     >>> class MyExpandedForm(form.Form):
@@ -1309,7 +1309,7 @@
 ----------------------
 
 We may want to indicate that some fields should be used for input even
-if the underlying schema field is readonly. We can do this using the
+if the underlying schema field is read-only. We can do this using the
 `for_input` option when setting up form_fields:
 
     >>> class MyForm(form.Form):

Modified: Zope3/trunk/src/zope/testbrowser/README.txt
===================================================================
--- Zope3/trunk/src/zope/testbrowser/README.txt	2006-02-22 20:17:54 UTC (rev 41756)
+++ Zope3/trunk/src/zope/testbrowser/README.txt	2006-02-23 13:49:34 UTC (rev 41757)
@@ -178,7 +178,7 @@
     >>> link.attrs
     {'href': 'navigate.html?message=By+Link+Text'}
 
-Links can be "clicked" and the brower will navigate to the refrenced URL.
+Links can be "clicked" and the browser will navigate to the referenced URL.
 
     >>> link.click()
     >>> browser.url
@@ -204,7 +204,7 @@
     '...Message: <em>By Link Text with Normalization</em>...'
 
 Note that clicking a link object after its browser page has expired will
-geterate an error.
+generate an error.
 
     >>> link.click()
     Traceback (most recent call last):
@@ -805,7 +805,7 @@
     >>> ctrl = browser.getControl(name='radio-value')
 
     This shows the existing value of the control, as it was in the
-    HTML recieved from the server:
+    HTML received from the server:
 
     >>> ctrl.value
     ['2']
@@ -958,7 +958,7 @@
 -----
 
 Because pages can have multiple forms with like-named controls, it is sometimes
-neccesary to access forms by name or id.  The browser's `forms` attribute can
+necessary to access forms by name or id.  The browser's `forms` attribute can
 be used to do so.  The key value is the form's name or id.  If more than one
 form has the same name or id, the first one will be returned.