summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLaurent Pinchart <laurent.pinchart@ideasonboard.com>2023-11-26 05:11:50 +0200
committerLaurent Pinchart <laurent.pinchart@ideasonboard.com>2023-11-28 14:08:13 +0200
commit64be677b11b70177f730cee6c787809e9e27c737 (patch)
tree824ec4cf41a99f010f8f6b06e4dcfdec72f91e1a
parent74c5db6fd412a414ea3c38bbb5436849d4bd8d34 (diff)
Documentation: Fix list indentation
reStructuredText requires list items to be indented. Fix the few offenders in the documentation. Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
-rw-r--r--Documentation/python-bindings.rst10
-rw-r--r--README.rst8
2 files changed, 9 insertions, 9 deletions
diff --git a/Documentation/python-bindings.rst b/Documentation/python-bindings.rst
index bac5cd34..ed9f686b 100644
--- a/Documentation/python-bindings.rst
+++ b/Documentation/python-bindings.rst
@@ -17,13 +17,13 @@ chapter lists the differences.
Mostly these differences fall under two categories:
1. Differences caused by the inherent differences between C++ and Python.
-These differences are usually caused by the use of threads or differences in
-C++ vs Python memory management.
+ These differences are usually caused by the use of threads or differences in
+ C++ vs Python memory management.
2. Differences caused by the code being work-in-progress. It's not always
-trivial to create a binding in a satisfying way, and the current bindings
-contain simplified versions of the C++ API just to get forward. These
-differences are expected to eventually go away.
+ trivial to create a binding in a satisfying way, and the current bindings
+ contain simplified versions of the C++ API just to get forward. These
+ differences are expected to eventually go away.
Coding Style
------------
diff --git a/README.rst b/README.rst
index 4a6eb252..a8b91a26 100644
--- a/README.rst
+++ b/README.rst
@@ -188,8 +188,8 @@ the build.ninja module. This is a snippet of the error message.
This can be solved in two ways:
-1) Don't install meson again if it is already installed system-wide.
+1. Don't install meson again if it is already installed system-wide.
-2) If a version of meson which is different from the system-wide version is
-already installed, uninstall that meson using pip3, and install again without
-the --user argument.
+2. If a version of meson which is different from the system-wide version is
+ already installed, uninstall that meson using pip3, and install again without
+ the --user argument.