diff --git a/responses/02_repo-owner-answer.md b/responses/02_repo-owner-answer.md
index 2abc358..00b0f78 100644
--- a/responses/02_repo-owner-answer.md
+++ b/responses/02_repo-owner-answer.md
@@ -5,15 +5,20 @@ A repository _does_ exist at githubtraining/training-manual, but it is private.
 ![gif of repository, pointing to ownership by githubtraining organization, and to a private visibility](https://user-images.githubusercontent.com/6351798/56159957-32413700-5f83-11e9-90f6-c1b64ade39c4.gif)
 
 <details>
-<summary>Why can't you see it then? Review the <b>Files Changed</b> tab and see if you can figure it out. Collapse this text if you'd like an explanation.</summary>
+<summary>Why can't you see it then? Review the <b>Files Changed</b> tab and see if you can figure it out. Expand this text if you'd like an explanation.</summary>
 
-The repository `training-manual` in the @githubtraining organization is private. It's only visible to members of that organization. If you're not a member of the organization, it'll appear like the repository doesn't exist to you. This is an example of why having the right ownership structure is important. Having too many organizations with restrictive permissions silos and isolates each organization's work.
-</summary>
+## Understanding repository visibility
+
+There are three types of repository visiility: **public, internal, and private**. 
+
+Our repository, `githubtraining/training-manual`, isn't public. It could be internal, which means only members of the organizations that an account owns will see it, or it could be private, which means only teams and individuals that have been granted access to it can see it. 
+
+This is an example of why having the right ownership structure is important. Otherwise, it can be difficult for members of your team to find and contribute to projects. Having too many disconnected organizations with restrictive permissions silos and isolates each organization's work.
 
 Here are some recommendations based on some :sparkles: use of GitHub that we've seen:
-- Aim for as few organizations as possible. Remember, each organization is a black box to those outside of that organization.
+- Use the internal visibility (currently in beta) if you're working on behalf of an [enterprise account](https://help.github.com/en/articles/about-enterprise-accounts).
 - Name your repositories in a meaningful manner. Usually a simple project or application name will suffice.
-</summary>
+<hr>
 </details>
 
 Please merge this pull request.