Update readme.txt

Author: ganeshmohan02

Fortimanager_4/readme.txt

@@ -7,21 +7,21 @@
 
 Prework task list:
 ******************
-1.	Create the new sub-interface on the new L3out with access of  [ping, FM].
+1.	Create the new sub-interface on the new L3out with access to [ping, FM].
 2.	Associate the new Sub-interface into existing Zone-interface / create the new Zone-interface.
-3.	Configure the static route next-hop to the new L3out.
-4.	Create/modify the access-list and update the prefixes into access-list.
-5.	Only update the new prefixes into the access-list, even if we run multiples time the same script, to avoid duplicate prefix entries in the access-list.
-6.	Create/update the route-map, finally associate the access-list into the route-map.
-7.	In OSPF, associate route-map filter on static redistribution. 
+3.	Configure the new static route with next-hop of new L3out.
+4.	Create/modify the access-list and update the news prefixes into access-list.
+5.	Condition: Append only the new prefix into access-list, even if we run multiples time the same script, this will avoid duplicate prefix entries in the access-list.
+6.	Create/update the route-map, and then associate the access-list into route-map.
+7.	In OSPF, associate route-map filter with static redistribution enabled. 
 8.	Push all the configuration to the Fortigate appliance.
 
-Cutover plan:
+Cutover plan:  Traffic will swithover via new L3out interface.
 ***********
 1.	Disable the current physical/vlan interface.
 2.	Push all the configuration to the Fortigate appliance.
 
-Rollback plan:
+Rollback plan: Traffic will swithover back to the old interface.
 ************
 1.	Enable the current physical/vlan interface.
 2.	Push all the configuration to the Fortigate appliance.