Fixing a typo in the ipa-rmkeytab man page.
Over the past few months I also found a few typos in docstrings and
comments. I'm including those in the patch.
--
Petr³
From ccbd83e7dd07fb896994e8898515c271919efc63 Mon Sep 17 00:00:00 2001
From: Petr Viktorin <[email protected]>
Date: Tue, 5 Jun 2012 09:11:34 -0400
Subject: [PATCH] Typo fixes
---
Contributors.txt | 2 +-
ipa-client/man/ipa-rmkeytab.1 | 2 +-
ipalib/output.py | 4 ++--
ipaserver/plugins/dogtag.py | 8 ++++----
4 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/Contributors.txt b/Contributors.txt
index 6abd2d68261c7d09251cd2d1527efc05920e04a0..94cf047266656af4d6bcefe7ac01749d59fe7c04 100644
--- a/Contributors.txt
+++ b/Contributors.txt
@@ -19,7 +19,7 @@ Developers:
Rich Megginson
Martin Nagy
Simo Sorce
- Petr ViktorÃn
+ Petr Viktorin
Andrew Wnuk
Adam Young
Jan Zeleny
diff --git a/ipa-client/man/ipa-rmkeytab.1 b/ipa-client/man/ipa-rmkeytab.1
index 11618d1b5f583c07e4fec50f8c849dc923bacb88..4f4fcee2665c105c5cdab5f964e3295bea4b7997 100644
--- a/ipa-client/man/ipa-rmkeytab.1
+++ b/ipa-client/man/ipa-rmkeytab.1
@@ -37,7 +37,7 @@ contain the name of the service, the hostname of the
server, and the realm name.
ipa\-rmkeytab provides two ways to remove principals.
-A specific principal can be removed or all principals for all
+A specific principal can be removed or all
principals for a given realm can be removed.
All encryption types and versions of a principal are removed.
diff --git a/ipalib/output.py b/ipalib/output.py
index 1202ee19923bd6710a4c4e82a108d79ec63251b8..1f42b4d6ee1395448e2fa67f0c2552b601c35410 100644
--- a/ipalib/output.py
+++ b/ipalib/output.py
@@ -49,8 +49,8 @@ class Output(ReadOnly):
If you have values that you don't want to be printed then add
``'no_display'`` to flags.
- The difference between ``'no_dipslay`` and ``'no_output'`` is
- that ``'no_output`` will prevent a Param value from being returned
+ The difference between ``'no_display'`` and ``'no_output'`` is
+ that ``'no_output'`` will prevent a Param value from being returned
at all. ``'no_display'`` will cause the API to return a value, it
simply won't be displayed to the user. This is so some things may
be returned that while not interesting to us, but may be to others.
diff --git a/ipaserver/plugins/dogtag.py b/ipaserver/plugins/dogtag.py
index b56e04f4d8675c34cc5e7db42a1b45402ef79084..8accb56d2c070f22d1841ecd2fbdf73295211309 100644
--- a/ipaserver/plugins/dogtag.py
+++ b/ipaserver/plugins/dogtag.py
@@ -203,7 +203,7 @@
>>> doc.xpath("//book/*[starts-with(name(), 'chapter')]/section[2]")
-The built-in starts-with() returns true if it's first argument starts with it's
+The built-in starts-with() returns true if its first argument starts with its
second argument. Thus the example above says if the node name of the second
location step begins with 'chapter' consider it a match and the search
proceeds to the next location step, which in this example is any node named
@@ -214,7 +214,7 @@
expression extension. EXSLT extensions are accessed by using XML
namespaces. The regular expression name space identifier is 're:' In lxml we
need to pass a set of namespaces to XPath object constructor in order to allow
-it to bind to those namespaces during it's evaluation. Then we just use the
+it to bind to those namespaces during its evaluation. Then we just use the
EXSLT regular expression match() function on the node name. Here is how this is
done:
@@ -227,8 +227,8 @@
function which we bind to the name 'find'. We've passed it a set of namespaces
as a dict via the 'namespaces' keyword parameter of etree.XPath(). The predicate
for the second location step uses the 're:' namespace to find the function name
-'match'. The re:match() takes a string to search as it's first argument and a
-regular expression pattern as it's second argument. In this example the string
+'match'. The re:match() takes a string to search as its first argument and a
+regular expression pattern as its second argument. In this example the string
to seach is the node name of the location step because we called the built-in
node() function of XPath. The regular expression pattern we've passed says it's
a match if the string begins with 'chapter' is followed by any number of
--
1.7.10.2
_______________________________________________
Freeipa-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/freeipa-devel
