Skip to content

Commit df24702

Browse files
committed
Update docs
1 parent a42d125 commit df24702

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

docs/translations.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,15 +14,14 @@ If there's not, then today is your day to lead this effort! Here's how to start:
1414

1515
## Keeping a translation updated
1616

17-
Git is pretty good at making it easy to see what files have changed. We'll try to make it as easy as possible for you to keep your translation up to date.
17+
Git is pretty good at tracking files that have changed. We'll try to make it as easy as possible for you to keep your translation up to date.
1818

19-
These directions assume you have two [remotes](https://git-scm.com/docs/git-remote) configured for your local clone of is repository.
20-
21-
0. `origin` - the translation fork. If you didn't originally clone this from the fork, you can update it with `git mote set-url origin https://github.com/[yourname]/open-source-guide.git`
22-
0. `upstream` - `git remote add upstream https://github.com/github/open-source-guide.git`
19+
Note: These directions assume the `origin` [remote](https://git-scm.com/docs/git-remote) is the translation fork. If you didn't originally clone the repository from the fork, you can update it with `git remote set-url origin https://github.com/[yourname]/opensource.guide.git`.
2320

2421
Here is the recommended process:
2522

2623
0. Run `$ script/sync-translation` to merge the latest changes from upstream and open a Pull Request on your fork.
2724
0. If files requiring translation have been modified, they will be added to a checklist in the Pull Request.
2825
0. Once all files have been updated, merge the pull request.
26+
27+
Run this script as often as you want to keep your translation up to date.

0 commit comments

Comments
 (0)