doc: README.md - format "Troubleshooting"

Format "Troubleshooting" into its own section so that it doesn't confuse
readers of the vstart installation procedure.

This PR is part of a series of PRs meant to preserve the integrity of
the README.md file after some recent additions that break the flow of
the document.

This PR follows https://github.com/ceph/ceph/pull/61221.

Signed-off-by: Zac Dover <zac.dover@proton.me>

diff --git a/README.md b/README.md
index 3c781e532f320dcc682763416cb55f4de281fe07..a3fdfada623c3e0819f5fb5ca36ace33a3258394 100644 (file)
--- a/README.md
+++ b/README.md
@@ -137,15 +137,14 @@ To build Ceph, follow this procedure:
    * Preserve Existing Data skip cluster reinitialization between tests by
      using the `-n` flag.
 
-    > [TROUBLESHOOTING]
-    >
-    >Cluster Fails to Start: Look for errors in the logs under the out/ directory, e.g.
-    >
-    >OSD Crashes: Check the OSD logs for errors.
-    >
-    >Cluster in a Health Error State: Run `ceph status` to identify the issue.
-    >
-    >RocksDB Errors: Look for RocksDB-related errors in OSD logs.
+##  Troubleshooting     
+ 
+    * Cluster Fails to Start: Look for errors in the logs under the `out/`
+      directory.
+    * OSD Crashes: Check the OSD logs for errors.
+    * Cluster in a `Health Error` State: Run the `ceph status` command to
+      identify the issue.
+    * RocksDB Errors: Look for RocksDB-related errors in the OSD logs.
     
     To manage a vstart cluster, stop daemons using `./stop.sh` and start them with ./vstart.sh --daemon osd.${ID} [--nodaemonize]. 
     Restart by stopping and restarting daemons, ensuring no stale sockets.