fix lists in communicating-on-github.md (#33100)

content/get-started/using-github/communicating-on-github.md

@@ -22,7 +22,7 @@
 
 {% data variables.product.product_name %} provides built-in collaborative communication tools allowing you to interact closely with your community. This quickstart guide will show you how to pick the right tool for your needs.
 
 {% ifversion discussions %}
   {% ifversion team-discussions %}
   You can create and participate in issues, pull requests, {% data variables.product.prodname_discussions %}, and team discussions, depending on the type of conversation you'd like to have.
   {% else %}
@@ -34,36 +34,36 @@
 
 ### {% data variables.product.prodname_github_issues %}
 
-- are useful for discussing specific details of a project such as bug reports, planned improvements and feedback.
-- are specific to a repository, and usually have a clear owner.
-- are often referred to as {% data variables.product.prodname_dotcom %}'s bug-tracking system.
+- Are useful for discussing specific details of a project such as bug reports, planned improvements and feedback
+- Are specific to a repository, and usually have a clear owner
+- Are often referred to as {% data variables.product.prodname_dotcom %}'s bug-tracking system
 
 ### Pull requests
 
-- allow you to propose specific changes.
-- allow you to comment directly on proposed changes suggested by others.
-- are specific to a repository.
+- Allow you to propose specific changes
+- Allow you to comment directly on proposed changes suggested by others
+- Are specific to a repository
 
 {% ifversion fpt or ghec %}
 
 ### {% data variables.product.prodname_discussions %}
 
-- are like a forum, and are best used for open-form ideas and discussions where collaboration is important.
-- may span many repositories.
-- provide a collaborative experience outside the codebase, allowing the brainstorming of ideas, and the creation of a community knowledge base.
-- often don’t have a clear owner.
-- often do not result in an actionable task.
+- Are like a forum, and are best used for open-form ideas and discussions where collaboration is important
+- May span many repositories
+- Provide a collaborative experience outside the codebase, allowing the brainstorming of ideas, and the creation of a community knowledge base
+- Often don’t have a clear owner
+- Often do not result in an actionable task
 {% endif %}
 
 {% ifversion team-discussions %}
 
 ### Team discussions
 
 - can be started on your team's page for conversations that span across projects and don't belong in a specific issue or pull request. Instead of opening an issue in a repository to discuss an idea, you can include the entire team by having a conversation in a team discussion.
 - allow you to hold discussions with your team about planning, analysis, design, user research and general project decision making in one place.{% ifversion ghes %}
 - provide a collaborative experience outside the codebase, allowing the brainstorming of ideas.
 - often don’t have a clear owner.
 - often do not result in an actionable task.{% endif %}
 {% endif %}
 
 ## Which discussion tool should I use?
@@ -109,7 +109,7 @@
 - The user creates a pull request with the fix.
 - A repository maintainer reviews the pull request, comments on it, and merges it.
 
 {% ifversion discussions %}
 
 ### Scenarios for {% data variables.product.prodname_discussions %}
 
@@ -140,7 +140,7 @@
 
 This example shows a team post for the `octo-team` team.
 
 ![Example of team discussion.](/assets/images/help/projects/team-discussions-example.png)
 
 The `octocat` team member posted a team discussion, informing the team of various things:
 - A team member called Mona started remote game events.
@@ -156,7 +156,7 @@
 
 For pull requests, you can create draft pull requests if your proposed changes are still a work in progress. Draft pull requests cannot be merged until they're marked as ready for review. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#draft-pull-requests)."
 
 {% ifversion discussions %}
 For {% data variables.product.prodname_discussions %}, you can{% ifversion fpt or ghec %} set up a code of conduct and{% endif %} pin discussions that contain important information for your community. For more information, see "[AUTOTITLE](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
 {% endif %}