Help: Fix wrong return values for unset inherited properties

Since ff6234509e (Help: Clarify behavior of INHERITED properties, 2018-03-21),
the docs for some get_..._property() commands incorrectly describe
the behavior for inherited properties. When a property is not set, even
in a parent scope, the returned result from the get_..._property()
command is the same whether the property is inherited or not.
The docs incorrectly stated that an empty string would be returned
for inherited properties in such cases.

1 files changed, 5 insertions, 7 deletions

diff --git a/Help/command/get_target_property.rst b/Help/command/get_target_property.rst
index f4135cf..1554a85 100644
--- a/Help/command/get_target_property.rst
+++ b/Help/command/get_target_property.rst
@@ -8,13 +8,11 @@ Get a property from a target.
   get_target_property(<variable> <target> <property>)
 
 Get a property from a target.  The value of the property is stored in the
-specified ``<variable>``.  If the target property is not found, the behavior
-depends on whether it has been defined to be an ``INHERITED`` property
-or not (see :command:`define_property`).  Non-inherited properties will set
-``<variable>`` to ``<variable>-NOTFOUND``, whereas inherited properties will
-search the relevant parent scope as described for the :command:`define_property`
-command and if still unable to find the property, ``<variable>`` will be set to
-an empty string.
+specified ``<variable>``.  If the target property is not found, ``<variable>``
+will be set to ``<variable>-NOTFOUND``.  If the target property was defined to
+be an ``INHERITED`` property (see :command:`define_property`), the search will
+include the relevant parent scopes, as described for the
+:command:`define_property` command.
 
 Use :command:`set_target_properties` to set target property values.
 Properties are usually used to control how a target is built, but some