(Named Features): Explain subfeatures better.

diff --git a/lispref/loading.texi b/lispref/loading.texi
index eb576f8fbbc4b6c011de3d1e9d9d9cd8121aa03d..150e20275b1487b406be0583eb909e6f48a9b2b6 100644 (file)
--- a/lispref/loading.texi
+++ b/lispref/loading.texi
@@ -726,8 +726,14 @@ The argument @var{feature} must be a symbol.  @code{provide} returns
 @var{feature}.
 
 If provided, @var{subfeatures} should be a list of symbols indicating
-a set of specific subfeatures provided by this version of @var{feature}.
-You can test the presence of a subfeature using @code{featurep}.
+a set of specific subfeatures provided by this version of
+@var{feature}.  You can test the presence of a subfeature using
+@code{featurep}.  The idea of subfeatures is that you use them when a
+package (which is one @var{feature}) is complex enough to make it
+useful to give names to various parts or functionalities of the
+package, which might or might not be loaded, or might or might not be
+present in a given version.  @xref{Network Feature Testing}, for
+an example.
 
 @smallexample
 features