diff --git a/public-validator-+-sentry/buildvalidatorsentry.md b/public-validator-+-sentry/buildvalidatorsentry.md
index 1e0f3d3b..12c5327d 100644
--- a/public-validator-+-sentry/buildvalidatorsentry.md
+++ b/public-validator-+-sentry/buildvalidatorsentry.md
@@ -216,7 +216,7 @@ For the following instructions, we will describe the steps to setup a validator
     blzd start
     ```
 
-    the node will start and catch up to the rest of the zone. Occasionally, this command will fail, in that case run the following command first
+    The node will start and catch up to the rest of the zone. Occasionally, this command will fail, in that case run the following command first
 
     ```text
     blzd unsafe-reset-all
@@ -224,6 +224,12 @@ For the following instructions, we will describe the steps to setup a validator
 
     and then retry the start command.
 
+    Notes.
+    
+    i. If you want extra info for logging or analysis or debugging purposes, you can alternatively add the `--log_level info` flag to `blzd start`. 
+    
+    ii. Don't get alarmed if you are following the **REHEARSAL** PATH and your validator starts up stating it is not a validator. This is NORMAL. Your validator is currently in jail, so it does not appear in the active validator set. That's all this message means.
+
 22. If you are creating a validator, wait till your new node catches up to the rest of the zone. It will be obvious as the node will slow down output and be getting blocks every 4-5 seconds. 
 
     To be sure, run the following command in another terminal on the validator and look for the output of `true`: