[libcamera-devel,v2,4/6] docs: Markup LD_PRELOAD as code
diff mbox series

Message ID 20200605082618.3793785-5-marvin.schmidt1987@gmail.com
State Accepted
Commit 46b3402b594db599f9f13c70c520d598711daeb8
Headers show
Series
  • Random documentation fixes
Related show

Commit Message

Marvin Schmidt June 5, 2020, 8:26 a.m. UTC 
LD_PRELOAD is an environment variable, use code markup to reflect that
semantic

Signed-off-by: Marvin Schmidt <marvin.schmidt1987@gmail.com>
Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
---
 Documentation/docs.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Patch
diff mbox series 

diff --git a/Documentation/docs.rst b/Documentation/docs.rst
index 873d8cd..f4c6ec5 100644
--- a/Documentation/docs.rst
+++ b/Documentation/docs.rst
@@ -148,7 +148,7 @@  V4L2 Compatibility Layer
 
 The project shall support traditional V4L2 application through an additional
 libcamera wrapper library. The wrapper library shall trap all accesses to
-camera devices through LD_PRELOAD, and route them through libcamera to
+camera devices through `LD_PRELOAD`, and route them through libcamera to
 emulate a high-level V4L2 camera device. It shall expose camera device
 features on a best-effort basis, and aim for the level of features
 traditionally available from a UVC camera designed for video conferencing.
@@ -380,7 +380,7 @@  V4L2 Compatibility Layer
 V4L2 compatibility is achieved through a shared library that traps all
 accesses to camera devices and routes them to libcamera to emulate high-level
 V4L2 camera devices. It is injected in a process address space through
-LD_PRELOAD and is completely transparent for applications.
+`LD_PRELOAD` and is completely transparent for applications.
 
 The compatibility layer exposes camera device features on a best-effort basis,
 and aims for the level of features traditionally available from a UVC camera