X-Git-Url: http://erislabs.net/gitweb/?a=blobdiff_plain;f=doc%2Fverify.texi;h=c661d469dc57f8844460e4b71fc12f98566f0ae3;hb=adff17f337187985ea8c62b961fde5c9544911aa;hp=a978e432aaef33974af0c4126d220d682737cf59;hpb=1602f0afed21be664fcf5c42d59db07cc22c56d6;p=gnulib.git

diff --git a/doc/verify.texi b/doc/verify.texi
index a978e432a..c661d469d 100644
--- a/doc/verify.texi
+++ b/doc/verify.texi
@@ -50,11 +50,11 @@ integer constant expression, then a compiler might reject a usage like
 @samp{verify (@var{V});} even when @var{V} is
 nonzero.
 
-Although the standard @code{assert} macro is a runtime test, draft C1X
+Although the standard @code{assert} macro is a runtime test, C11
 specifies a builtin @code{_Static_assert (@var{V},
 @var{STRING-LITERAL})}, its @file{assert.h} header has a similar macro
-named @code{static_assert}, and draft C++0X has a similar
-@code{static_assert} builtin.  These draft builtins and macros differ
+named @code{static_assert}, and C++11 has a similar
+@code{static_assert} builtin.  These builtins and macros differ
 from @code{verify} in two major ways.  First, they can also be used
 within a @code{struct} or @code{union} specifier, in place of an
 ordinary member declaration.  Second, they require the programmer to