From: Guido van Rossum <guido@python.org>
Date: Wed, 3 Dec 2008 04:18:17 +0000 (+0000)
Subject: Fix bad markup.
X-Git-Tag: v3.0~11
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b768d4f759bf8677fac8f6eae4f720be02dc6d78;p=python

Fix bad markup.
---

diff --git a/Doc/whatsnew/3.0.rst b/Doc/whatsnew/3.0.rst
index c195f53d25..2c2e168d36 100644
--- a/Doc/whatsnew/3.0.rst
+++ b/Doc/whatsnew/3.0.rst
@@ -221,10 +221,10 @@ changed.
   hold text is :class:`str`, the type used to hold data is
   :class:`bytes`.  The biggest difference with the 2.x situation is
   that any attempt to mix text and data in Python 3.0 raises
-  :ext:`TypeError`, whereas if you were to mix Unicode and 8-bit
+  :exc:`TypeError`, whereas if you were to mix Unicode and 8-bit
   strings in Python 2.x, it would work if the 8-bit string happened to
   contain only 7-bit (ASCII) bytes, but you would get
-  :ext:`UnicodeDecodeError` if it contained non-ASCII values.  This
+  :exc:`UnicodeDecodeError` if it contained non-ASCII values.  This
   value-specific behavior has caused numerous sad faces over the
   years.