diff options
| author | ivanhoe <ivanhoe@fiscari.de> | 2022-06-04 03:54:32 -0500 |
|---|---|---|
| committer | ivanhoe <ivanhoe@fiscari.de> | 2022-06-04 03:54:32 -0500 |
| commit | 1775849e22dff84a745fb41c06c1541d2ccc3dce (patch) | |
| tree | cff21c3503cac9799edaf43e057ee382579b8637 /doc | |
| parent | aa88af0b7bdd57f3b872b3267a325474270886d9 (diff) | |
| download | pidgin-1775849e22dff84a745fb41c06c1541d2ccc3dce.tar.gz | |
fix typos in code contributions guide
Testing Done:
None
Reviewed at https://reviews.imfreedom.org/r/1493/
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/reference/libpurple/code_contributions.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/reference/libpurple/code_contributions.md b/doc/reference/libpurple/code_contributions.md index dc2fc48e3e..b571f1a4e9 100644 --- a/doc/reference/libpurple/code_contributions.md +++ b/doc/reference/libpurple/code_contributions.md @@ -244,7 +244,7 @@ publish, so if you do not selectively push commits, all of your draft commits will be published. You can name this additional clone whatever you like, but using something like `pidgin-clean` is a fairly common practice. This makes it easy for you to know that this clone is only meant for landing review requests, -and other admistrative work like updating the ChangeLog and COPYRIGHT files. +and other administrative work like updating the ChangeLog and COPYRIGHT files. When you are ready to land a review request you need to make sure you are on the proper branch. In most cases this will be the branch named ***default*** @@ -308,7 +308,7 @@ before the patch was applied. The `--no-backup` argument says to not save the changes that you are reverting and the `--all` argument tells Mercurial to revert all files. -### Cleaning up a Landed of Discarded Review Request +### Cleaning up a Landed or Discarded Review Request Whether or not your pull request has been accepted, you probably want to clean it up from your local repository. To do so, you need to update to a branch |