Clarifying Implementation Steps of Drive Docs 7.1

[mdueltgen]

🗣 Description

Updated 7.1 steps for editing rules for clarity.

💭 Motivation and context

Closes #451 Based on Internal Discussion about clarifying steps for rule configuration polices

🧪 Testing

N/A no code changes.

✅ Pre-approval checklist

• [x] This PR has an informative and human-readable title.
• [x] Changes are limited to a single goal - eschew scope creep!
• [x] If applicable, All future TODOs are captured in issues, which are referenced in the PR description.
• [x] The relevant issues PR resolves are linked preferably via closing keywords.
• [x] All relevant type-of-change labels have been added.
• [x] I have read and agree to the CONTRIBUTING.md document.
• [x] These code changes follow cisagov code standards.
• [x] All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
• [ ] Tests have been added and/or modified to cover the changes in this PR.
• [ ] All new and existing tests pass.

✅ Pre-merge Checklist

• [ ] This PR has been smoke tested to ensure main is in a functional state when this PR is merged.
• [ ] Squash all commits into one PR level commit using the Squash and merge button.

✅ Post-merge Checklist

• [ ] Delete the branch to clean up.
• [ ] Close issues resolved by this PR if the closing keywords did not activate.

[mdueltgen]

Since we have decided to move DLP to common controls I will close this PR