Skip to content

Commit 71a4bed

Browse files
committed
docs: change letter cases in titles
1 parent 14bfd1f commit 71a4bed

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

contributing/workflow.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ Clone your repository, leaving a local folder for you to work with:
6666
> git clone ORIGIN_URL
6767
```
6868

69-
## Syncing your repository
69+
## Syncing Your Repository
7070

7171
Within your local repository, Git will have created an alias,
7272
**origin**, for the GitHub repository it is bound to. You want to create
@@ -179,11 +179,11 @@ For instance, to commit your work from a debugging session:
179179

180180
Just make sure that your commits in a feature branch are all related.
181181

182-
### Changing a commit message
182+
### Changing a Commit Message
183183

184184
See <https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message>.
185185

186-
### When you work on two features
186+
### When You Work on Two Features
187187

188188
If you are working on two features at a time, then you will want to
189189
switch between them to keep the contributions separate. For instance:
@@ -318,7 +318,7 @@ And finally push your local branch to your GitHub repository:
318318
> git push --force-with-lease origin fix/problem123
319319
```
320320

321-
## If you sent to the wrong branch
321+
## If You Sent to the Wrong Branch
322322

323323
If you have sent a PR to the wrong branch, you need to create a new PR branch.
324324

0 commit comments

Comments
 (0)