Fix the errors in the document descriptions of 'To move a policy' and…

… 'fortios_firewall_security_policyseq'

website/docs/guides/fgt_policymove.html.md

@@ -1,7 +1,7 @@
 ---
 subcategory: ""
 layout: "fortios"
-page_title: "To move the policy"
+page_title: "To move a policy"
 description: |-
   Methods used to move the position of a policy, relative to another policy, in the sequence order of how policies are applied.
 ---
@@ -346,5 +346,5 @@ Methods used to move the position of a policy, relative to another policy, in th
     ```
     We can find that policy 4 has been moved to after 7.
 
-## Last words
-If you need to move a policy urgently, option II is the better choice. If you want to be consistent with Terraform, then option I is the better choice. Option III just provides an another additional method. You can choose one of these methods to move a policy according to your needs.
+## Conclusion
+If a policy needs to be moved urgently, option II is the better choice. If the configuration needs to be consistent with terraform, then option I is the better choice. Option III just provides an another additional method. Choose one of these methods to move a policy as needed.

website/docs/r/fortios_firewall_security_policyseq.html.markdown

@@ -83,7 +83,7 @@ The following attributes are exported:
 * `enable_state_checking` - Enable status detection for policy_src_id and policy_dst_id
 * `state_policy_srcdst_pos` - The parameter is read-only, it is used to get the lastest relative position of the policy with policy_src_id and the policy with policy_dst_id when enable_state_checking is set to true. This can help check whether the latest relative position of the two plicies matches the configuration, and help check whether they have been deleted. This is generally used in the following situations: These two policies are deleted or moved outside of Terraform. Terraform plan will determine the consistency of the state based on this attribute. It includs the following states:
   * ""(empty string): the lastest relative position of the two plicies is same as the configuration.
-  * Similar to "policy with policy_src_id(3) is 1 ahead of policy with policy_dst_id(5)" or "policy with policy_src_id(3) is 4 behind policy with policy_dst_id(5)" : The lastest relative position of the two plicies doesn't match the configuration and terraform outputs the relative position offset. Here 5 and 3 here are the policyid of the corresponding policy
+  * Similar to "policy with policy_src_id(3) is 1 ahead of policy with policy_dst_id(5)" or "policy with policy_src_id(3) is 4 behind policy with policy_dst_id(5)" : The lastest relative position of the two plicies doesn't match the configuration and terraform outputs the relative position offset. Here 5 and 3 are the policyid of the corresponding policy
   * Similar to "policy with policy_dst_id(5) was deleted" or "policy with policy_src_id(3) was deleted" or "policies with policy_src_id(3) and policy_dst_id(5) were deleted":  It indicates that one or both of these two policies have been deleted outside of terraform.
 * `state_policy_list` - The parameter is read-only, it is used to get the latest policy list(by sequence) for reference when enable_state_checking is set to true, in the list, the policy with policy_src_id and the policy with policy_dst_id will be marked with * . It will be updated after each terraform apply or terraform refresh.
 * `comment` - Comment