Update content/ui-patterns/degraded-experiences.mdx

Co-authored-by: Natalya Shelburne <[email protected]>

content/ui-patterns/degraded-experiences.mdx

@@ -58,7 +58,7 @@ Before making a decision about how to handle UI with unavailable content, check
 
 ### Replacing UI with a message
 
-We don't want users to think they've suffered data loss. If we know a user created something, don't show a generic "empty state". It's better to explain that it's unavailable, or remove the entire section from the page (including the section's heading). For example, I might think my repositories were deleted if I'm on an organization page (like [https://github.com/primer/](https://github.com/primer/)) and the repositories aren't listed there.
+We don't want users to think they've suffered data loss. Instead of a generic "empty state, it is better to explain that it's unavailable, or remove the entire section from the page (including the section's heading). For example, as a user, I might think my repositories were deleted if I am on an organization page (like [https://github.com/primer/](https://github.com/primer/)) and the repositories aren't listed there.
 
 <img
   width="960"