Skip to content

Improve clarity in documentation wording#43461

Open
24f2001045-DS wants to merge 1 commit intogithub:mainfrom
24f2001045-DS:patch-1
Open

Improve clarity in documentation wording#43461
24f2001045-DS wants to merge 1 commit intogithub:mainfrom
24f2001045-DS:patch-1

Conversation

@24f2001045-DS
Copy link

What

Improved clarity in documentation by refining sentence wording.

Why

The updated wording removes redundancy and improves readability.

Changes

  • Minor wording improvement

Notes

This is a documentation-only change. Verified manually.

Why:

Closes:

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

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 an 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 review environment.

## What
Improved clarity in documentation by refining sentence wording.

## Why
The updated wording removes redundancy and improves readability.

## Changes
- Minor wording improvement

## Notes
This is a documentation-only change. Verified manually.
@welcome
Copy link

welcome bot commented Mar 20, 2026

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 github-actions bot added the triage Do not begin working on this issue until triaged by the team label Mar 20, 2026
@github-actions
Copy link
Contributor

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
get-started/using-github/github-flow.md fpt
ghec
ghes@ 3.20 3.19 3.18 3.17 3.16 3.15 3.14
fpt
ghec
ghes@ 3.20 3.19 3.18 3.17 3.16 3.15 3.14

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@Sharra-writes
Copy link
Contributor

@24f2001045-DS I would change "what" to "the," but otherwise retain the use of "the commit" instead of "it," because the paragraph is talking about both commits and branches, and we prioritize clarity over pleasant word flow. If you want to make that change, I'll accept this.

@Sharra-writes Sharra-writes added content This issue or pull request belongs to the Docs Content team get started Content related to "Getting Started" doc set Waiting on contributor and removed triage Do not begin working on this issue until triaged by the team labels Mar 20, 2026
@djsbsspa-creator
Copy link


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 get started Content related to "Getting Started" doc set Waiting on contributor

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants