Add syntax highlighting

docs/getting_started/faq.rst

@@ -175,6 +175,7 @@ Querying an ID3D11Device for UUID ``{A7AA6116-9C8D-4BBA-9083-B4D816B71B78}`` wil
 
     It's unlikely the extension will ever be 'made official', so these enumerants can be used:
 
+.. highlight:: c++
 .. code:: c++
 
     #define GL_DEBUG_TOOL_EXT                 0x6789

docs/getting_started/tips_tricks.rst

@@ -24,6 +24,7 @@ This page is a random hodge-podge of different tips and tricks that might not be
 #. You can close tabs by middle clicking on them.
 #. You can trigger a capture from code. renderdoc.dll exports an :doc:`in_application_api` for this purpose, defined in ``renderdoc_app.h`` in the distributions:
 
+   .. highlight:: c++
    .. code:: c++
 
        #include "renderdoc_app.h"
@@ -49,6 +50,7 @@ This page is a random hodge-podge of different tips and tricks that might not be
 #. To get API debug or error messages, enable "Create Debug Device" when capturing then check out the :doc:`../window/debug_messages` window.
 #. Detecting RenderDoc from your code can either be done by trying to load and use the renderdoc :doc:`in_application_api`, or through API specific ways:
 
+   .. highlight:: c++
    .. code:: c++
 
        // For D3D11:
@@ -68,6 +70,7 @@ This page is a random hodge-podge of different tips and tricks that might not be
 
 #. RenderDoc can be informed about separated debug shader blobs through API specific ways:
 
+   .. highlight:: c++
    .. code:: c++
 
        // For D3D11: