Added more warnings about ni's demise.
diff --git a/Doc/lib/libni.tex b/Doc/lib/libni.tex
index c564373..faa1b8b 100644
--- a/Doc/lib/libni.tex
+++ b/Doc/lib/libni.tex
@@ -4,9 +4,14 @@
\strong{Warning: This module is obsolete.} As of Python 1.5a4,
package support (with different semantics for \code{__init__} and no
-support for \code{__domain__} or\code{__}) is built in the
+support for \code{__domain__} or \code{__}) is built in the
interpreter. The ni module is retained only for backward
-compatibility.
+compatibility. As of Python 1.5b2, it has been renamed to \code{ni1};
+if you really need it, you can use \code{import ni1}, but the
+recommended approach is to rely on the built-in package support,
+converting existing packages if needed. Note that mixing \code{ni}
+and the built-in package support doesn't work once you import
+\code{ni}, all packages use it.
The \code{ni} module defines a new importing scheme, which supports
packages containing several Python modules. To enable package
diff --git a/Doc/libni.tex b/Doc/libni.tex
index c564373..faa1b8b 100644
--- a/Doc/libni.tex
+++ b/Doc/libni.tex
@@ -4,9 +4,14 @@
\strong{Warning: This module is obsolete.} As of Python 1.5a4,
package support (with different semantics for \code{__init__} and no
-support for \code{__domain__} or\code{__}) is built in the
+support for \code{__domain__} or \code{__}) is built in the
interpreter. The ni module is retained only for backward
-compatibility.
+compatibility. As of Python 1.5b2, it has been renamed to \code{ni1};
+if you really need it, you can use \code{import ni1}, but the
+recommended approach is to rely on the built-in package support,
+converting existing packages if needed. Note that mixing \code{ni}
+and the built-in package support doesn't work once you import
+\code{ni}, all packages use it.
The \code{ni} module defines a new importing scheme, which supports
packages containing several Python modules. To enable package