summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--doc/daily_work.rst10
-rw-r--r--doc/ptx-theme/theme.conf2
-rw-r--r--doc/ref_manual.rst3
3 files changed, 9 insertions, 6 deletions
diff --git a/doc/daily_work.rst b/doc/daily_work.rst
index 0575726e2..0490e9030 100644
--- a/doc/daily_work.rst
+++ b/doc/daily_work.rst
@@ -258,10 +258,10 @@ the QEMU in the first console as:
platform-<platformname>/root-debug$ qemu-<architecture> -g 1234 -cpu <cpu-core> -L . usr/bin/myapp
.. note:: PTXdist always builds two root filesystems. ``root/`` and
-``root-debug/``. ``root/`` contains all components without debug
-information (all binaries are in the same size as used later on on the
-real target), while all components in ``root-debug/`` still containing
-the debug symbols and are much bigger in size.
+ ``root-debug/``. ``root/`` contains all components without debug
+ information (all binaries are in the same size as used later on on the
+ real target), while all components in ``root-debug/`` still containing
+ the debug symbols and are much bigger in size.
The added *-g 1234* parameter lets QEMU wait for a GDB connection to run
the application.
@@ -384,7 +384,7 @@ command line parameters.
limit the system load to the given value.
.. Important:: using ``-ji`` and ``-je`` can overload the system
-immediatley. These settings are very hard.
+ immediatley. These settings are very hard.
A much softer setup is to just use the ``-j<number>`` parameter. This will run
up to ``<number>`` tasks at the same time which will be spread over everything
diff --git a/doc/ptx-theme/theme.conf b/doc/ptx-theme/theme.conf
index ebae6b94b..362414ed9 100644
--- a/doc/ptx-theme/theme.conf
+++ b/doc/ptx-theme/theme.conf
@@ -1,3 +1,3 @@
[theme]
-inherit = default
+inherit = classic
stylesheet = ptx.css
diff --git a/doc/ref_manual.rst b/doc/ref_manual.rst
index cdb5ab136..658e5721e 100644
--- a/doc/ref_manual.rst
+++ b/doc/ref_manual.rst
@@ -596,6 +596,9 @@ Note: The package's install stage must be 'DESTDIR' aware to be able to make
it install its content into the corresponding packages directory (in our example
``<platform-dir>/packages/foo-1.0.0/`` here).
+
+.. _param_macros:
+
ptx/endis
~~~~~~~~~