Doc: update term "namespace package"

Recommend using regular package officially to avoid
people just think `__init__.py` is not necessary.

Author: methane

Doc/glossary.rst

@@ -936,11 +936,17 @@ Glossary
       modules, respectively.
 
    namespace package
-      A :pep:`420` :term:`package` which serves only as a container for
-      subpackages.  Namespace packages may have no physical representation,
+      A :term:`package` which serves only as a container for subpackages.
+      Namespace packages may have no physical representation,
       and specifically are not like a :term:`regular package` because they
       have no ``__init__.py`` file.
 
+      Namespace packages allow you to split single package across multiple directories or distributions.
+      On the other hand, namespace packages have some drawbacks and pitfalls.
+      Use :term:`regular package` always when it fits your needs.
+
+      For more information, see :pep:`420` and :ref:`reference-namespace-package`.
+
       See also :term:`module`.
 
    nested scope

Doc/reference/import.rst

@@ -123,6 +123,8 @@ Importing ``parent.one`` will implicitly execute ``parent/__init__.py`` and
 ``parent/three/__init__.py`` respectively.
 
 
+.. _reference-namespace-package:
+
 Namespace packages
 ------------------