diff --git a/docs/Installation.md b/docs/Installation.md
index 0401774a..fd53ca22 100644
--- a/docs/Installation.md
+++ b/docs/Installation.md
@@ -139,6 +139,25 @@ print board is not connected with USB to the host, due to some boards
 being able to feed power back to the board and stopping a flash from
 occurring.
 
+Please note, that most print boards that use SD cards for flash will
+implement some kind of flash loop protection for when the sd card is left
+in place. There are two common methods:
+
+Filename Change Required (usually "stock" print boards):
+
+These boards require the firmware file to have a different name each
+time you flash (for example, firmware1.bin, firmware2.bin, etc.).
+If you reuse the same filename, the board may ignore it and not update.
+
+Automatic File Renaming (usually aftermarket print boards:
+
+Other boards allow using the same filename, commonly firmware.bin,
+but after flashing, the board renames the file to firmware.cur.
+This helps indicate the firmware was successfully flashed and prevents
+it from flashing again on the next startup.
+
+Before flashing, make sure to check which behavior your board follows.
+
 For common micro-controllers using Atmega chips, for example the 2560,
 the code can be flashed with something
 similar to: