summaryrefslogtreecommitdiffstats
path: root/ipalib
diff options
context:
space:
mode:
authorYuri Chornoivan <yurchor@ukr.net>2012-09-16 19:35:56 +0300
committerMartin Kosek <mkosek@redhat.com>2012-09-18 08:45:28 +0200
commit8bbb42b4102b62b215ece59b8b6561af13891e9e (patch)
treea98291d0f82003d4a09ddd579f501b2f3b106fa8 /ipalib
parentf695f79748ffd0782990ec752ed140648347d632 (diff)
downloadfreeipa-8bbb42b4102b62b215ece59b8b6561af13891e9e.tar.gz
freeipa-8bbb42b4102b62b215ece59b8b6561af13891e9e.tar.xz
freeipa-8bbb42b4102b62b215ece59b8b6561af13891e9e.zip
Fix various typos.
https://fedorahosted.org/freeipa/ticket/3089
Diffstat (limited to 'ipalib')
-rw-r--r--ipalib/errors.py2
-rw-r--r--ipalib/plugins/automember.py2
-rw-r--r--ipalib/plugins/dns.py6
-rw-r--r--ipalib/plugins/idrange.py6
-rw-r--r--ipalib/plugins/internal.py2
-rw-r--r--ipalib/plugins/sudorule.py4
-rw-r--r--ipalib/plugins/trust.py4
-rw-r--r--ipalib/plugins/user.py2
-rw-r--r--ipalib/session.py4
9 files changed, 16 insertions, 16 deletions
diff --git a/ipalib/errors.py b/ipalib/errors.py
index 42181d2d2..6a4e2c5d6 100644
--- a/ipalib/errors.py
+++ b/ipalib/errors.py
@@ -446,7 +446,7 @@ class XMLRPCMarshallError(PublicError):
class RefererError(PublicError):
"""
- **911** Raised when the the request does not contain an HTTP referer
+ **911** Raised when the request does not contain an HTTP referer
For example:
diff --git a/ipalib/plugins/automember.py b/ipalib/plugins/automember.py
index 40359604b..0a7f37319 100644
--- a/ipalib/plugins/automember.py
+++ b/ipalib/plugins/automember.py
@@ -29,7 +29,7 @@ __doc__ = _("""
Auto Membership Rule.
Bring clarity to the membership of hosts and users by configuring inclusive
-or exclusive regex paterns, you can automatically assign a new entries into
+or exclusive regex patterns, you can automatically assign a new entries into
a group or hostgroup based upon attribute information.
A rule is directly associated with a group by name, so you cannot create
diff --git a/ipalib/plugins/dns.py b/ipalib/plugins/dns.py
index d71607f28..562f23a01 100644
--- a/ipalib/plugins/dns.py
+++ b/ipalib/plugins/dns.py
@@ -63,7 +63,7 @@ value can be used, they just should not be combined in one add operation. When
modifying an existing entry, new RR specific options can be used to change
one part of a DNS record, where the standard option for raw value is used
to specify the modified value. The following example demonstrates
-a modification of MX record preference form 0 to 1 in a record without
+a modification of MX record preference from 0 to 1 in a record without
modifying the exchanger:
ipa dnsrecord-mod --mx-rec="0 mx.example.com." --mx-preference=1
@@ -120,7 +120,7 @@ EXAMPLES:
ipa dnsrecord-add example.com @ --loc-rec="49 11 42.4 N 16 36 29.6 E 227.64m"
Add new A record for www.example.com. Create a reverse record in appropriate
- reverse zone as well. In this case a PTR record "2" pointing to www.example.com.
+ reverse zone as well. In this case a PTR record "2" pointing to www.example.com
will be created in zone 15.142.80.in-addr.arpa.
ipa dnsrecord-add example.com www --a-rec=80.142.15.2 --a-create-reverse
@@ -182,7 +182,7 @@ EXAMPLES:
Show records for resource www in zone example.com
ipa dnsrecord-show example.com www
- Forward all request for a zone external.com to another nameserver using
+ Forward all requests for the zone external.com to another nameserver using
a "first" policy (it will send the queries to the selected forwarder and if
not answered it will use global resolvers):
ipa dnszone-add external.com
diff --git a/ipalib/plugins/idrange.py b/ipalib/plugins/idrange.py
index 9604e1666..efa906428 100644
--- a/ipalib/plugins/idrange.py
+++ b/ipalib/plugins/idrange.py
@@ -104,7 +104,7 @@ and the base-id has to be added to get the Posix ID.
Typically the creation of ID ranges happens behind the scenes and this CLI
must not be used at all. The ID range for the local domain will be created
during installation or upgrade from an older version. The ID range for a
-trusted domain will be create together with the trust by 'ipa trust-add ...'.
+trusted domain will be created together with the trust by 'ipa trust-add ...'.
The use cases for this CLI are
USE CASES:
@@ -119,7 +119,7 @@ USE CASES:
If the ID range of the local domain is exhausted, i.e. no new IDs can be
assigned to Posix users or groups by the DNA plugin, a new range has to be
- created to allow new users an groups to be added. (Currently there is no
+ created to allow new users and groups to be added. (Currently there is no
connection between this range CLI and the DNA plugin, but a future version
might be able to modify the configuration of the DNS plugin as well)
@@ -261,7 +261,7 @@ class idrange_add(LDAPCreate):
Additionally
--rid-base
- --econdary-rid-base
+ --secondary-rid-base
may be given for a new ID range for the local domain while
diff --git a/ipalib/plugins/internal.py b/ipalib/plugins/internal.py
index 09e08be13..4dc409cd3 100644
--- a/ipalib/plugins/internal.py
+++ b/ipalib/plugins/internal.py
@@ -245,7 +245,7 @@ class i18n_messages(Command):
"refresh": _("Refresh the page."),
"reload": _("Reload the browser."),
"main_page": _("Return to the main page and retry the operation"),
- "title": _("An error has occured (${error})"),
+ "title": _("An error has occurred (${error})"),
},
"errors": {
"error": _("Error"),
diff --git a/ipalib/plugins/sudorule.py b/ipalib/plugins/sudorule.py
index 8359c3336..111080999 100644
--- a/ipalib/plugins/sudorule.py
+++ b/ipalib/plugins/sudorule.py
@@ -32,9 +32,9 @@ commands as root or another user while providing an audit trail of the
commands and their arguments.
FreeIPA provides a means to configure the various aspects of Sudo:
- Users: The user(s)/group(s) allowed to envoke Sudo.
+ Users: The user(s)/group(s) allowed to invoke Sudo.
Hosts: The host(s)/hostgroup(s) which the user is allowed to to invoke Sudo.
- Allow Command: The specific command(s) permited to be run via Sudo.
+ Allow Command: The specific command(s) permitted to be run via Sudo.
Deny Command: The specific command(s) prohibited to be run via Sudo.
RunAsUser: The user(s) or group(s) of users whose rights Sudo will be invoked with.
RunAsGroup: The group(s) whose gid rights Sudo will be invoked with.
diff --git a/ipalib/plugins/trust.py b/ipalib/plugins/trust.py
index 074560dc2..9d77549ad 100644
--- a/ipalib/plugins/trust.py
+++ b/ipalib/plugins/trust.py
@@ -138,7 +138,7 @@ class trust_add(LDAPCreate):
),
Password('realm_passwd?',
cli_name='password',
- label=_("Active directory domain adminstrator's password"),
+ label=_("Active directory domain administrator's password"),
confirm=False,
),
Str('realm_server?',
@@ -299,7 +299,7 @@ class trust_mod(LDAPUpdate):
__doc__ = _("""
Modify a trust (for future use).
- Currently only the default option to modify the LDAP attributes are
+ Currently only the default option to modify the LDAP attributes is
available. More specific options will be added in coming releases.
""")
diff --git a/ipalib/plugins/user.py b/ipalib/plugins/user.py
index 84a63dfa6..e6eb0d9cb 100644
--- a/ipalib/plugins/user.py
+++ b/ipalib/plugins/user.py
@@ -56,7 +56,7 @@ about this topic please see: ipa help passwd
Account lockout on password failure happens per IPA master. The user-status
command can be used to identify which master the user is locked out on.
-It is on that master the the administrator must unlock the user.
+It is on that master the administrator must unlock the user.
EXAMPLES:
diff --git a/ipalib/session.py b/ipalib/session.py
index 87fa44825..36beececd 100644
--- a/ipalib/session.py
+++ b/ipalib/session.py
@@ -230,7 +230,7 @@ Proposed Solution
Our interface to the web server is via WSGI which invokes a callback
per request passing us an environmental context for the request. For
-this discussion we'll name the the WSGI callback "application()", a
+this discussion we'll name the WSGI callback "application()", a
conventional name in WSGI parlance.
Shared session data will be handled by memcached. We will create one
@@ -304,7 +304,7 @@ in the future. Session data may not be available because:
Cookie manipulation is done via the standard Python Cookie module.
Session cookies will be set to only persist as long as the browser has
-the session open. They will be tagged so the the browser only returns
+the session open. They will be tagged so the browser only returns
the session ID on SSL secured HTTP requests. They will not be visible
to Javascript in the browser.