To explain what GHE.com means - Enterprise Managed Users GitHub

[tahershaakir]

Why:

In the document its not clear ( and confusing) as to what GHE.com means.
Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Adding some text in brackets next to GHE.com to explain what it is

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require a SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the preview environment.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

👓 Previews for changed content

This comment is 🤖 automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the review server. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
copilot/setting-up-github-copilot/setting-up-github-copilot-for-your-enterprise.md	ghec	ghec

---

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server
This table is posted from the Content Changes Table Comment workflow.

[nguyenalex836]

@tahershaakir Thanks so much for opening a PR! I'll get this triaged for review ✨

[subatoi]

Hi, thanks for your contribution, but I'm afraid we won't be accepting this on this occasion. I'm sorry this was confusing, but I'm not sure that the suggested addition is appropriate—if your plan includes GitHub Support, I'd recommend reaching out to them for help. We're always updating our docs, and you're welcome to check any issues in this repo marked help wanted if you'd like to work on any as part of our community. Many thanks again!

[tahershaakir]

@subatoi I have always found GitHub's documentation to be very good ( much better than some other Enterprise Applications :-)). I guess one of the reasons could be the ease with which you'll 'facilitate' updates by actual users reading them and trying to make use of them ( Which in most cases is not very easy to get feedback from)

I was 'unsure' about the GHE.com mention on that page and thus made the suggestion.
Of course you folks would know the right way and wording to make it better and self serving versus asking GitHub support every time :-).

Thanks.

[subatoi]

@tahershaakir Thanks so much for providing further insight—as you can appreciate, we get a lot of feedback, and I'll pass yours on to the relevant teams.

What I will say is that we're currently working on revising this documentation set (one of the reasons we'd be reluctant to accept any contributions right now)—I can't give you a specific timeframe, but I hope that when those improvements go live, it will improve the experience further for you.

Thank you again!