Tutorial: Fix typos and mislabeled code blocks

Help/guide/tutorial/Configuration and Cache Variables.rst

@@ -200,7 +200,7 @@ To change this we have two options. First, we can edit the file which stores
 the cache variables between CMake configuration runs, the "CMake Cache". This
 file is ``build/CMakeCache.txt``, in it we can find the option cache variable.
 
-.. code-block:: cmake
+.. code-block:: text
 
   //Build the Tutorial executable
   TUTORIAL_BUILD_UTILITIES:BOOL=OFF

Help/guide/tutorial/Finding Dependencies.rst

@@ -414,7 +414,7 @@ Exercise 3 - Finding Other Kinds of Files
 
 In a perfect world every dependency we care about would be packaged correctly,
 or at least some other developer would have written a module that discovers it
-for us. We do no live in a perfect world, and sometimes we will have to get
+for us. We do not live in a perfect world, and sometimes we will have to get
 our hands dirty and discover build requirements manually.
 
 For this we have the other find commands enumerated earlier in the step, such

Help/guide/tutorial/In-Depth CMake Library Concepts.rst

@@ -69,7 +69,7 @@ otherwise it will be ``STATIC``.
   add_library(MyLib-static STATIC)
   add_library(MyLib-shared SHARED)
 
-  # Depends on BUILD_SHARED_LIBRARY
+  # Depends on BUILD_SHARED_LIBS
   add_library(MyLib)
 
 This is desirable behavior, as it allows packagers to determine what kind of

Help/guide/tutorial/In-Depth CMake Target Commands.rst

@@ -292,7 +292,7 @@ Sometimes, we need to exercise specific control over the exact options being
 passed on the compile and link line. These situations are addressed by
 :command:`target_compile_options` and :command:`target_link_options`.
 
-.. code:: c++
+.. code:: cmake
 
   target_compile_options(MyApp PRIVATE -Wall -Werror)
   target_link_options(MyApp PRIVATE -T LinksScript.ld)