Help: Package without components should use 'check_required_components' too

Macro 'check_required_components' should be called even if there are no
components provided by package.  This will make sure error is reported
in next cases:

    find_package(Foo CONFIG REQUIRED oops) # 'oops' treated as component
    find_package(Foo CONFIG REQUIRED COMPONENTS foo) # no components expected

Modules/CMakePackageConfigHelpers.cmake

@@ -102,13 +102,15 @@
 # into the ``FooConfig.cmake`` file.
 #
 # ``check_required_components(<package_name>)`` should be called at the end of
-# the ``FooConfig.cmake`` file if the package supports components.  This macro
+# the ``FooConfig.cmake`` file. This macro checks whether all requested,
-# checks whether all requested, non-optional components have been found, and if
+# non-optional components have been found, and if this is not the case, sets
-# this is not the case, sets the ``Foo_FOUND`` variable to ``FALSE``, so that
+# the ``Foo_FOUND`` variable to ``FALSE``, so that the package is considered to
-# the package is considered to be not found.  It does that by testing the
+# be not found.  It does that by testing the ``Foo_<Component>_FOUND``
-# ``Foo_<Component>_FOUND`` variables for all requested required components.
+# variables for all requested required components.  This macro should be
-# When using the ``NO_CHECK_REQUIRED_COMPONENTS_MACRO`` option, this macro is
+# called even if the package doesn't provide any components to make sure
-# not generated into the ``FooConfig.cmake`` file.
+# users are not specifying components erroneously.  When using the
+# ``NO_CHECK_REQUIRED_COMPONENTS_MACRO`` option, this macro is not generated
+# into the ``FooConfig.cmake`` file.
 #
 # For an example see below the documentation for
 # :command:`write_basic_package_version_file()`.