Merge pull request #8286 from rajbos/rajbos-patch-1

Clarified the organizations that get visibility on 'internal' repositories

Author: lecoursen

content/admin/user-management/managing-organizations-in-your-enterprise/index.md

@@ -5,7 +5,7 @@ redirect_from:
   - /enterprise/admin/categories/admin-bootcamp/
   - /enterprise/admin/user-management/organizations-and-teams
   - /enterprise/admin/user-management/managing-organizations-in-your-enterprise
-intro: 'Organizations are great for creating distinct groups of users within your company, such as divisions or groups working on similar projects. {% ifversion ghae %}Internal{% else %}Public and internal{% endif %} repositories that belong to an organization are accessible to users in other organizations, while private repositories are inaccessible to anyone but members of the organization that are granted access.'
+intro: 'Organizations are great for creating distinct groups of users within your company, such as divisions or groups working on similar projects. {% ifversion ghae %}Internal{% else %}Public and internal{% endif %} repositories that belong to an organization are accessible to members of other organizations in the enterprise, while private repositories are inaccessible to anyone but members of the organization that are granted access.'
 versions:
   ghes: '*'
   ghae: '*'
@@ -22,4 +22,3 @@ children:
   - /continuous-integration-using-jenkins
 shortTitle: Manage organizations
 ---
-