From 5678446bcab8c3fafd7bf2524cb37ab6f0e75981 Mon Sep 17 00:00:00 2001 From: "Joshua M. Boniface" Date: Mon, 29 Jul 2019 00:03:45 -0400 Subject: [PATCH] Fix indenting on sublist --- docs/architecture/daemon.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/architecture/daemon.md b/docs/architecture/daemon.md index 1d6e40a8..abb283fa 100644 --- a/docs/architecture/daemon.md +++ b/docs/architecture/daemon.md @@ -42,9 +42,9 @@ The daemon startup sequence is documented below. The main daemon entrypoint is ` 0. The node begins setting up the object representations of resources, in order: - a. Node entries - b. Network entries, creating client networks and starting them as required. - c. Domain (VM) entries, starting up the VMs as required. - d. Ceph storage entries (OSDs, Pools, Volumes, Snapshots). + a. Node entries + b. Network entries, creating client networks and starting them as required. + c. Domain (VM) entries, starting up the VMs as required. + d. Ceph storage entries (OSDs, Pools, Volumes, Snapshots). 0. The node activates its keepalived timer and begins sending keepalive updates to the cluster. The daemon state transitions from `init` to `run` and the system has started fully.