summaryrefslogtreecommitdiff
path: root/Doc/library/string.rst
diff options
context:
space:
mode:
authorGeorg Brandl <georg@python.org>2008-01-11 12:58:40 +0000
committerGeorg Brandl <georg@python.org>2008-01-11 12:58:40 +0000
commit0b4e0f5a4597e4ee9c6c1f9a4ba65fb6ea34210c (patch)
tree6433c2b4647af9229bd5b36ab6b1a6a0e7be8c2a /Doc/library/string.rst
parent1dfa4dc548efe7a1a11fcef9fb69ccf73f60196d (diff)
downloadcpython-0b4e0f5a4597e4ee9c6c1f9a4ba65fb6ea34210c.tar.gz
Fix markup.
Diffstat (limited to 'Doc/library/string.rst')
-rw-r--r--Doc/library/string.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/Doc/library/string.rst b/Doc/library/string.rst
index 41b8a49760..7cd28b0db1 100644
--- a/Doc/library/string.rst
+++ b/Doc/library/string.rst
@@ -230,8 +230,8 @@ as a string, overriding its own definition of formatting. By converting the
value to a string before calling :meth:`__format__`, the normal formatting logic
is bypassed.
-Two conversion flags are currently supported: ``'!s'`` which calls :func:`str()`
-on the value, and ``'!r'`` which calls :func:`repr()`.
+Two conversion flags are currently supported: ``'!s'`` which calls :func:`str`
+on the value, and ``'!r'`` which calls :func:`repr`.
Some examples::
@@ -289,7 +289,7 @@ Most built-in types implement the following options for format specifications,
although some of the formatting options are only supported by the numeric types.
A general convention is that an empty format string (``""``) produces the same
-result as if you had called :func:`str()` on the value.
+result as if you had called :func:`str` on the value.
The general form of a *standard format specifier* is: