From 3f921d30fe488c957d7190b56f9bcd44999cd42d Mon Sep 17 00:00:00 2001 From: Johanna England Date: Fri, 10 May 2024 13:31:59 +0200 Subject: [PATCH] Fix typo/formatting in kbd role in documentation --- doc/hacking/using-docker.rst | 2 +- doc/howto/commandline-utilities.rst | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/hacking/using-docker.rst b/doc/hacking/using-docker.rst index f80bc12ca5..159770effd 100644 --- a/doc/hacking/using-docker.rst +++ b/doc/hacking/using-docker.rst @@ -135,7 +135,7 @@ A complete rebuild of the NAV code can be initiated by:: Rebuilding the containers ~~~~~~~~~~~~~~~~~~~~~~~~~ -Running :kdb:`docker compose up` will normally build the container images, +Running :kbd:`docker compose up` will normally build the container images, before starting them, if they don't exist already. However, if the image definitions have changed (e.g. when you are switching between development branches or changed the :file:`Dockerfile` definitions, or any of the files diff --git a/doc/howto/commandline-utilities.rst b/doc/howto/commandline-utilities.rst index 629a8942d7..b485cd09f0 100644 --- a/doc/howto/commandline-utilities.rst +++ b/doc/howto/commandline-utilities.rst @@ -17,8 +17,8 @@ processes and cron jobs, regardless of whether you are running under SysV init system, systemd or other process control systems. If NAV doesn't appear to be doing anything, the first order of business is -checking the state of its background processes with the command :kbd:`nav -status` +checking the state of its background processes with the command +:kbd:`nav status` Usage