Fix markup.

diff --git a/Doc/library/string.rst b/Doc/library/string.rst
index 41b8a497600e2b86a740f2eda240b94f1bdf21c3..7cd28b0db1742eddb7eb7134031ecef83468cd1a 100644 (file)
--- 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: