doc: markup kapow as program role

Co-authored-by: Roberto Abdelkader Martínez Pérez <robertomartinezp@gmail.com>

docs/source/concepts/request_life_cycle.rst

@@ -14,14 +14,14 @@ The user makes a request to the `User HTTP Interface`.
 
 - The request is matched against the route table.
 
-- ``kapow`` provides a `HANDLER_ID` to identify this request and don't mix it
+- :program:`kapow` provides a `HANDLER_ID` to identify this request and don't mix it
   with other requests that could be running concurrently.
 
 
 2. spawn
 --------
 
-``kapow`` spawns the executable specified as entrypoint in the matching
+:program:`kapow` spawns the executable specified as entrypoint in the matching
 route.
 
 The default entrypoint is ``/bin/sh``; let's focus on this workflow.
@@ -58,7 +58,7 @@ The shell dies.  Long live the shell!
 5. response
 -----------
 
-``kapow`` finalizes the original request.  Enjoy your banana now.
+:program:`kapow` finalizes the original request.  Enjoy your banana now.
 
 
 .. todo::

docs/source/the_project/quickstart.rst

@@ -139,7 +139,7 @@ Explanation:
 Launch the Service
 ++++++++++++++++++
 
-At this point we only need to launch ``kapow`` with our ``ping.pow``:
+At this point we only need to launch :program:`kapow` with our ``ping.pow``:
 
 .. code-block:: console