[OpenMP][doc]Minor doc fixes

[markdewing]

Summary

In SupportAndFAQ.rst, add blank lines before and after a bullet list and
sublist. This avoids an "Unepxected indentation" warning.

In Runtimes.rst, adjust the suggestion for setting LIBOMPTARGET_INFO.
The right shifts are not necessary as the bit mask values are already
correct.

[jdoerfert]

LG

@jhuber6 @tianshilei1992 if either of you happen to commit things, pick this up please :)

openmp/docs/SupportAndFAQ.rst

 
 It is a recent addition to LLVM and the implementation differs from that which
 has been shipping in ROCm and AOMP for some time. Early adopters will encounter
 bugs.
 
 Q: What are the LLVM components used in offloading and how are they found?
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 The libraries used by an executable compiled for target offloading are:
+
 - ``libomp.so`` (or similar), the host openmp runtime
 - ``libomptarget.so``, the target-agnostic target offloading openmp runtime
 - plugins loaded by libomptarget.so:
+
   - ``libomptarget.rtl.amdgpu.so``
   - ``libomptarget.rtl.cuda.so``
   - ``libomptarget.rtl.x86_64.so``
   - ``libomptarget.rtl.ve.so``
   - and others
+
 - dependencies of those plugins, e.g. cuda/rocr for nvptx/amdgpu
 
 The compiled executable is dynamically linked against a host runtime, e.g.
 ``libomp.so``, and against the target offloading runtime, ``libomptarget.so``. These
 are found like any other dynamic library, by setting rpath or runpath on the
 executable, by setting ``LD_LIBRARY_PATH``, or by adding them to the system search.
 
 ``libomptarget.so`` has rpath or runpath (whichever the system default is) set to

openmp/docs/design/Runtimes.rst

``LIBOMPTARGET_INFO`` is given below.
     * Indicate when data is copied to and from the device: ``0x20``
 
 Any combination of these flags can be used by setting the appropriate bits. For
 example, to enable printing all data active in an OpenMP target region along
 with ``CUDA`` information, run the following ``bash`` command.
 
 .. code-block:: console
 
-   $ env LIBOMPTARGET_INFO=$((1 << 0x1 | 1 << 0x10)) ./your-application
+   $ env LIBOMPTARGET_INFO=$((0x1 | 0x10)) ./your-application
 
 Or, to enable every flag run with every bit set.
 
 .. code-block:: console
 
    $ env LIBOMPTARGET_INFO=-1 ./your-application
 
 For example, given a small application implementing the ``ZAXPY`` BLAS routine,