IntenseWebs/freeipa
3
0
Fork 0
mirror of https://salsa.debian.org/freeipa-team/freeipa.git synced 2025-02-25 18:55:28 -06:00
Code Issues Packages Projects Releases Wiki Activity

Typo fixes

Browse Source
This commit is contained in:
Petr Viktorin 2012-06-05 09:11:34 -04:00 committed by Rob Crittenden
parent f4d2f2a65b
commit ec5115a155
4 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Contributors.txt
View File

@ -19,7 +19,7 @@ Developers:
Rich Megginson
Martin Nagy
Simo Sorce
Petr Viktorín
Petr Viktorin
Andrew Wnuk
Adam Young
Jan Zeleny

2
ipa-client/man/ipa-rmkeytab.1
View File

@ -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.

4
ipalib/output.py
View File

@ -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.

8
ipaserver/plugins/dogtag.py
View File

@ -203,7 +203,7 @@ name begins with 'chapter' it's a match. Here is how you can do that.
>>> 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 @@ the test against the node name? In this case we can use the EXSLT regular
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 @@ What is happening here is that etree.XPath() has returned us an evaluator
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