diff options
| author | Aidan Fitzgerald <aidan-fitz@users.noreply.github.com> | 2019-03-09 16:15:45 -0500 |
|---|---|---|
| committer | techknowlogick <matti@mdranta.net> | 2019-03-09 16:15:45 -0500 |
| commit | f5cf9a8355c46fa5619c03465178b51171ac30b9 (patch) | |
| tree | 0163eb48ca238b03612176817449133cb31e34cf /docs/content/doc/help | |
| parent | 8fffb0616866cfe7a293b457d8703724666374cb (diff) | |
| download | gitea-f5cf9a8355c46fa5619c03465178b51171ac30b9.tar.gz gitea-f5cf9a8355c46fa5619c03465178b51171ac30b9.zip | |
Copyedit docs (#6275)
Diffstat (limited to 'docs/content/doc/help')
| -rw-r--r-- | docs/content/doc/help/seek-help.en-us.md | 2 | ||||
| -rw-r--r-- | docs/content/doc/help/troubleshooting.en-us.md | 12 |
2 files changed, 7 insertions, 7 deletions
diff --git a/docs/content/doc/help/seek-help.en-us.md b/docs/content/doc/help/seek-help.en-us.md index 69252a0956..36406b091f 100644 --- a/docs/content/doc/help/seek-help.en-us.md +++ b/docs/content/doc/help/seek-help.en-us.md @@ -20,7 +20,7 @@ menu: ## Bugs -If you found a bug, please create an [issue on Github](https://github.com/go-gitea/gitea/issues). +If you found a bug, please create an [issue on GitHub](https://github.com/go-gitea/gitea/issues). ## Chinese Support diff --git a/docs/content/doc/help/troubleshooting.en-us.md b/docs/content/doc/help/troubleshooting.en-us.md index 6eb440c612..664a51731e 100644 --- a/docs/content/doc/help/troubleshooting.en-us.md +++ b/docs/content/doc/help/troubleshooting.en-us.md @@ -19,7 +19,7 @@ This page contains some common seen issues and their solutions. ## SSH issues -For issues reaching repositories over `ssh` while the gitea web front-end, but +For issues reaching repositories over `ssh` while the Gitea web front-end, but `https` based git repository access works fine, consider looking into the following. ``` @@ -32,7 +32,7 @@ following things: * On the client: * Ensure the public and private ssh keys are added to the correct Gitea user. - * Make sure there are no issues in the remote url, ensure the name of the + * Make sure there are no issues in the remote url. In particular, ensure the name of the git user (before the `@`) is spelled correctly. * Ensure public and private ssh keys are correct on client machine. * Try to connect using ssh (ssh git@myremote.example) to ensure a connection @@ -43,7 +43,7 @@ following things: * Verify that the correct public keys are added to `.ssh/authorized_keys`. Try to run `Rewrite '.ssh/authorized_keys' file (for Gitea SSH keys)` on the Gitea admin panel. - * Read gitea logs. + * Read Gitea logs. * Read /var/log/auth (or similar). * Check permissions of repositories. @@ -69,14 +69,14 @@ In this case, look into the following settings: ## Missing releases after migrating repository with tags -To migrate an repository *with* all tags you need to do two things +To migrate an repository *with* all tags, you need to do two things: * Push tags to the repository: ``` git push --tags ``` - * (Re-)sync tags of all repositories within gitea: + * (Re-)sync tags of all repositories within Gitea: ``` gitea admin repo-sync-releases ``` @@ -90,7 +90,7 @@ batch response: Authentication required: Authorization error: <GITEA_LFS_URL>/in Check that you have proper access to the repository error: failed to push some refs to '<GIT_REPO_URL>' ``` -Have you checked the value of `LFS_HTTP_AUTH_EXPIRY` in your `app.ini` file? By default your LFS token will expire after 20 minutes. If you have a slow connection or a large file (or both) it may not finish uploading within the time limit. +Have you checked the value of `LFS_HTTP_AUTH_EXPIRY` in your `app.ini` file? By default, your LFS token will expire after 20 minutes. If you have a slow connection or a large file (or both), it may not finish uploading within the time limit. You may want to set this value to `60m` or `120m`. |