Extends 'which notation should I use' section in FAQ

[ctorgalson]

• git module fails to interpret bool parameter (assumes Unicode) - v1.9.2 #11524

SUMMARY

Expands documentation of "Which notation should I use?" in FAQ section.

See comment in #11524.

ISSUE TYPE

• Docs Pull Request

COMPONENT NAME

Docs.

ANSIBLE VERSION

  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/Users/ctorgalson/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python2.7/site-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 2.7.15 (default, Jul 23 2018, 21:27:06) [GCC 4.2.1 Compatible Apple LLVM 9.1.0 (clang-902.0.39.2)]

ADDITIONAL INFORMATION

I'm not sure what the docs use to process RST, so I have not used a named anchor in the PR to link to the specific section. I can update the PR if anyone can enlighten me on the right format for relative link to a named anchor in the docs.

[ansibot]

cc @acozine
click here for bot help

[bcoca]

#43724

[acozine]

@ctorgalson thanks for contributing to the documentation! We use sphinx to process our rST files. The correct syntax for anchors and links is:
.. _this_is_an_anchor:
:ref:'this_is_an_anchor' (but use backticks instead of single-quotes to surround the link) for a link with the text of the section header just under the anchor
:ref:'link text is different <this_is_an_anchor>' (again, use backticks not single-quotes) for a link with custom text

[acozine]

So for this specific example, you'd want :ref:'playbooks_variables'

[ctorgalson]

Thanks @acozine. I think this PR will probably fade away and #43724 will be merged instead, but I've updated the link just in case :)

[acozine]

@ctorgalson I think both additions have merit (this PR and #43724). Thanks for updating the link.