From a536fb96de24929339814bf830f6ac194b68503f Mon Sep 17 00:00:00 2001
From: obarun <eric@obarun.org>
Date: Mon, 14 Oct 2024 19:31:19 +1100
Subject: [PATCH] Typo fix

---
 doc/66-dbus-launch.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/doc/66-dbus-launch.md b/doc/66-dbus-launch.md
index 9d74617..c40c6e9 100644
--- a/doc/66-dbus-launch.md
+++ b/doc/66-dbus-launch.md
@@ -92,9 +92,12 @@ It ensures that you use the latest *D-Bus* file declarations by overwriting any
 
 ### Running time
 
-*66-dbus-launch* responds to kernel signals. A `SIGHUP` signal triggers a reading, parsing, translating and writting process.
+*66-dbus-launch* responds to kernel signals:
+
+A `SIGHUP` signal triggers a reading, parsing, translating and writting process.
 Synchronization of services can also be manually triggered via `66 reload dbus` or `66 signal -s HUP dbus`.
 It also synchronizes the available list of services between the launcher and the broke as follows:
+
 - If a *D-Bus* service file is removed, the launcher deactivates from the broker, executes `66 remove <service>`, and erases the corresponding *66* frontend file.
 - If a new *D-Bus* service is found, the launcher triggers the reading, parsing, translating and writting process, and activates the service in the broker.
 - For an existing service with the same name, the launcher executes `66 parse -f <service>` to ensure the latest *D-Bus* service declaration is used. Note that the service need to restarted for any changes to take effect.
-- 
GitLab