Skip to content

Commit 1a76f5e

Browse files
sirosenhugovk
andauthored
Apply suggestions from code review
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
1 parent 86f942c commit 1a76f5e

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

getting-started/quick-reference.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,12 +7,12 @@ Quick reference
77
Here are the basic steps needed to get set up and open a pull request.
88

99
This is meant as a checklist and cheat-sheet, not a comprehensive guide.
10-
For complete instructions please see the :ref:`setup guide <setup>` and the
10+
For complete instructions see the :ref:`setup guide <setup>` and the
1111
:ref:`pull request guide <pullrequest>`.
1212

1313

14-
Setup Git
15-
=========
14+
Set up Git
15+
==========
1616

1717
Install and set up ``Git``.
1818

@@ -136,7 +136,7 @@ see :ref:`"Updating NEWS and What's New in Python" <news-entry>`.
136136
Create pull requests
137137
--------------------
138138

139-
Create pull bequests on GitHub from your branches, on your fork, and make sure
139+
Create pull requests on GitHub from your branches, on your fork, and make sure
140140
to put the relevant issue number in ``gh-NNNNNN``` format in the pull request title.
141141
For example:
142142

@@ -168,7 +168,7 @@ See also, GitHub's documentation on `commenting on Pull Requests`_.
168168

169169
.. note::
170170

171-
In order to keep the commit history intact, please avoid squashing or amending
171+
In order to keep the commit history intact, avoid squashing or amending
172172
history and then force-pushing to the PR.
173173
Reviewers often want to look at individual commits.
174174

0 commit comments

Comments
 (0)