Fix formatting issues in documentation: Removed periods and added backticks

[lalithaar]

Removed periods, Use backticks to format references to the file names (instead of italics).

Why:

The bullet points were not complete sentences, and according to the style guide, lists with incomplete sentences should not end with periods. This change ensures the article follows the documentation style guide.

Closes: #35661
Closes: #35660
Closes: #35658
Closes: #35657

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
discussions/guides/best-practices-for-community-conversations-on-github.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
pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.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
actions/about-github-actions/understanding-github-actions.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	from reusable
actions/writing-workflows/about-workflows.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	from reusable
actions/security-for-github-actions/security-guides/using-githubs-security-features-to-secure-your-use-of-github-actions.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	from reusable
admin/managing-code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance.md	ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable
code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.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	from reusable
pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.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	from reusable

---

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