Skip to content

Conversation

@Harshil-Jani
Copy link
Contributor

Why:

Closes: #26290

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

Check off the following:

  • I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

    • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.
  • For content changes, I have completed the self-review checklist.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jul 2, 2023
@Harshil-Jani
Copy link
Contributor Author

Why

Sorry. What ?

@Harshil-Jani
Copy link
Contributor Author

I always learning about new things are you help me

This is a pull request(PR) which attempts to solve any raised concern about the project. In context of this pull request, I am trying to resolve a wording confusion on the github documentation regarding organization or enterprise. The issue was already triaged in #26290 . Now, If the change is good to be merged then someone from github team will come and merge this PR and the change will go live.

@cmwilson21 cmwilson21 added content This issue or pull request belongs to the Docs Content team waiting for review Issue/PR is waiting for a writer's review and removed triage Do not begin working on this issue until triaged by the team labels Jul 3, 2023
@cmwilson21
Copy link
Contributor

@Harshil-Jani Thanks for the PR! ⚡

And thank you for being kind in the comments above ✨

I'll get this triaged for review! In the meantime, if you'd like to find other ways to contribute, check out our help wanted section to find open issues you can work on. 💖

@cmwilson21
Copy link
Contributor

And welcome to the community! 🎉

@rachaelrenk rachaelrenk self-requested a review July 14, 2023 22:18
Copy link
Contributor

@rachaelrenk rachaelrenk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! ✨ Thanks for opening this PR @Harshil-Jani. I'll get it approved and added to the merge queue.

@rachaelrenk rachaelrenk added this pull request to the merge queue Jul 14, 2023
github-merge-queue bot pushed a commit that referenced this pull request Jul 14, 2023
Signed-off-by: Harshil Jani <[email protected]>
Co-authored-by: Rachael Rose Renk <[email protected]>
Merged via the queue into github:main with commit f46d498 Jul 14, 2023
@github-actions
Copy link
Contributor

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

content This issue or pull request belongs to the Docs Content team waiting for review Issue/PR is waiting for a writer's review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Change wording in enterprise team synchronization documentation from "organization" to "enterprise".

3 participants