explain what to do in case of truncation [ci skip]

docs/specification/corruption.rst

@@ -51,7 +51,12 @@ Recovering from data corruption can be hard and time-consuming. Here are two app
       ./scripts/wal2json/wal2json "$TMHOME/data/cs.wal/wal" > /tmp/corrupted_wal
 
   3. Search for a "CORRUPTED MESSAGE" line.
-  4. By looking at the previous message and the message after the corrupted one and looking at the logs, try to rebuild the message.
+  4. By looking at the previous message and the message after the corrupted one
+       and looking at the logs, try to rebuild the message. If the consequent
+       messages are marked as corrupted too (this may happen if length header
+       got corrupted or some writes did not make it to the WAL ~ truncation),
+       then remove all the lines starting from the corrupted one and restart
+       Tendermint.
 
   .. code:: bash