summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGeorg Brandl <georg@python.org>2008-01-11 12:58:40 (GMT)
committerGeorg Brandl <georg@python.org>2008-01-11 12:58:40 (GMT)
commit222e1279f8d4d271a74486081f77d7346ea93105 (patch)
treebe03f68ecb389f350c964c5ee8d14f8159c74727
parent3540b508844353add804a1ed48e0a73469c385ca (diff)
downloadcpython-222e1279f8d4d271a74486081f77d7346ea93105.zip
cpython-222e1279f8d4d271a74486081f77d7346ea93105.tar.gz
cpython-222e1279f8d4d271a74486081f77d7346ea93105.tar.bz2
Fix markup.
-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 41b8a49..7cd28b0 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: