Merge pull request #22640 from CallMeGreg/main

fixed typo in adopting GHAS phase 4

Author: sophietheking

content/code-security/adopting-github-advanced-security-at-scale/phase-4-create-internal-documentation.md

@@ -23,7 +23,7 @@ If you ran pilot programs, use the experiences and feedback from the teams invol
 
 If you skip creating internal documentation, your rollout won’t go at your intended pace. Creating internal documentation may slow the initial rollout by a week or two, but that time will be made up when developers can answer their own questions instead of coming to your team.
 
-Education is probably the most crucial part of the rollout as it teaches developers what to do in different situations. You should ensure developers are empowered to maintain the security of their repository and that the security team are authorized to verify both what developers are doing and that it's in the best interest of security. In additional to internal documentation, education can take the form of online sessions, Q&As, etc.
+Education is probably the most crucial part of the rollout as it teaches developers what to do in different situations. You should ensure developers are empowered to maintain the security of their repository and that the security team are authorized to verify both what developers are doing and that it's in the best interest of security. In addition to internal documentation, education can take the form of online sessions, Q&As, etc.
 
 {% note %}