Minor changes from comments

source/standards/storing-source-code/index.html.md.erb

@@ -104,8 +104,8 @@ Specifically:
 - Work created outside the DfE Digital organisation should be transferred into
   the DfE Digital organisation at the earliest opportunity.
   - [GitHub: Guide to transferring a repository](https://help.github.com/en/articles/transferring-a-repository)
-- The [Skills Funding Agency](https://github.com/SkillsFundingAgency/)
-  GitHub organisation is also used by the DfE
+- The [Skills Funding Agency](https://github.com/SkillsFundingAgency/) and [DfEAgileOps](https://github.com/dfeagiledevops)
+  GitHub organisations are also used by the DfE
   - Not the default for DfE-Digital
 
 If your account is added to a repository without the account being a member of the owning organisation,
@@ -128,7 +128,7 @@ You may use your personal GitHub account, but you should:
 
 There are a number of requirements repositories in DfE must meet in order to be compliant with service standards and [Secure by Design](https://cddo.blog.gov.uk/2024/02/07/getting-started-with-the-secure-by-design-approach/) principles.
 
-Repositories must:
+Repositories containing production/ service code must:
 
 - have branch protection turned on for the default branch in your repository either via traditional branch protection or via repository rules. Branch protection should include:
     - at least one approval before merging