diff --git a/RotorOps:-Mission-Creator-Guide.md b/RotorOps:-Mission-Creator-Guide.md
index 343e08b..860bdfc 100644
--- a/RotorOps:-Mission-Creator-Guide.md
+++ b/RotorOps:-Mission-Creator-Guide.md
@@ -184,6 +184,15 @@ You can find the names of the UI elements in this source file: https://github.co
 
 - endTrigger: set to false to disable inserting the mission win/lose trigger actions
 
+***Override Imported FARP objects***
+You can use alternative import templates to populate the various FARPs and bases used in mission generation.  For example, if you wanted your mission template to use a FOB instead of the standard logistics zone, you could include the line: ```staging_logistics_file: FOB_16_SPWN_WIDE_LIGHTED```
+The filename should not include the .miz extension.  Available options:
+- zone_farp_file
+- staging_logistics_file
+- logistics_farp_file
+- defensive_farp_file
+- zone_protect_file
+
 # How the script works
 In a generated mission, you will find a DO SCRIPT trigger action similar to this:
 ```