Minor tweaks to the skipped config wording and adding documentation

docsite/latest/rst/intro_configuration.rst

@@ -109,6 +109,15 @@ different locations::
 
 Most users will not need to use this feature.  See `developing_plugins` for more details
 
+display_skipped_hosts
+=====================
+
+If set to `False`, ansible will not display any status for a task that is skipped. The default behavior is to display skipped tasks::
+
+    #display_skipped_hosts=True
+
+Note that Ansible will always show the task header for any task, regardless of whether or not the task is skipped.
+
 error_on_undefined_vars
 =======================
 

examples/ansible.cfg

@@ -73,9 +73,10 @@ timeout = 10
 ansible_managed = Ansible managed: {file} modified on %Y-%m-%d %H:%M:%S by {uid} on {host}
 
 # by default, ansible-playbook will display "Skipping [host]" if it determines a task
-# should not be run on a host.  Set this to "no" if you don't want to see these "Skipping" 
-# messages.
-# display_skipped_hosts: yes 
+# should not be run on a host.  Set this to "False" if you don't want to see these "Skipping" 
+# messages. NOTE: the task header will still be shown regardless of whether or not the 
+# task is skipped.
+#display_skipped_hosts = True
 
 # by default (as of 1.3), Ansible will raise errors when attempting to dereference 
 # Jinja2 variables that are not set in templates or action lines. Uncomment this line