From: Fred Drake <fdrake@acm.org>
Date: Sun, 2 Apr 2006 03:30:06 +0000 (+0000)
Subject: fix markup error
X-Git-Tag: v2.5a1~80
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=1c0e3284f9263ff59ab198f4d5c25e411672ea34;p=python

fix markup error
---

diff --git a/Doc/whatsnew/whatsnew25.tex b/Doc/whatsnew/whatsnew25.tex
index f6ef967857..66bf0e759d 100644
--- a/Doc/whatsnew/whatsnew25.tex
+++ b/Doc/whatsnew/whatsnew25.tex
@@ -699,7 +699,7 @@ Brett Cannon and Guido van Rossum; implemented by Brett Cannon.}
 
 The NumPy developers had a problem that could only be solved by adding
 a new special method, \method{__index__}.  When using slice notation,
-as in \code{[\var{start}:\var{stop}:\var{step}], the values of the
+as in \code{[\var{start}:\var{stop}:\var{step}]}, the values of the
 \var{start}, \var{stop}, and \var{step} indexes must all be either
 integers or long integers.  NumPy defines a variety of specialized
 integer types corresponding to unsigned and signed integers of 8, 16,