Apply review suggestions

Author: pranavchoudhary-tech

getting-started/pull-request-lifecycle.rst

@@ -669,15 +669,15 @@ will merge in the latest changes from the base branch into the PR.
 If this still doesn't help with the failure on the PR, you can try
 to re-run that particular failed check.
 
-Note that the :guilabel:`Re-run jobs` button on GitHub Actions is only visible
-to Python core developers and triagers. If you have these permissions, go to
+The :guilabel:`Re-run jobs` button on GitHub Actions is only visible
+to Python core and triage teams. If you have these permissions, go to
 the red GitHub Action job, click on the :guilabel:`Re-run jobs` button on the
 top right, and select :guilabel:`Re-run failed jobs`. The button will only be
 present when all other jobs finished running.
 
 If you are a regular contributor and cannot see the button, you can ask a
 reviewer to re-run the failed jobs for you in a PR comment. Alternatively, you
-can re-trigger the CI by pushing an empty commit to your branch (e.g.
+can re-trigger the CI by pushing an empty commit to your branch (for example,
 ``git commit --allow-empty -m "Trigger CI"``), or by closing and re-opening
 your pull request.