Be sure to define 'description'

[MichaelChirico]

Why:

In Rdatatable/data.table#6692, we considered doing this definition ourselves, but decided that it's better for GitHub's own docs to be more explicit about the term.

The point is that 'description' may not be perfectly clear to a new user & is used several times on this page. Better to avoid potential frustration and be overly verbose about what 'description' 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.

[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]

Automatically generated comment ℹ️

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 staging site. 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
issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10

---

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

[nguyenalex836]

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

[MichaelChirico]

I have no context to offer improvements for the CI errors -- I leave it to the reviewer's judgment whether those should be addressed here or in a separate PR.

[felicitymay]

Many thanks for your help improving this article ✨

I have no context to offer improvements for the CI errors -- I leave it to the reviewer's judgment whether those should be addressed here or in a separate PR.

It looks as if the CI error is a problem with one of our internal workflows that was triggered when I added a label to indicate that this is ready to merge. It's not a required test, but I'll follow up on this internally.

You'll need to wait longer than usual for this PR to be merged and in production. We're resuming updates next week.

[MichaelChirico]

Take your time / no rush at all. Please prioritize other work first as appropriate. I will lose no sleep over the status of this PR :)

[github-actions]

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 ⚡