domi/forgejo-domi
1
0
Fork 0
forked from forgejo/forgejo
Code Pull requests Activity

Fix various documentation, user-facing, and source comment typos (#16367)

Browse source 
* Fix various doc, user-facing, and source comment typos

Found via `codespell -q 3 -S ./options/locale,./vendor -L ba,pullrequest,pullrequests,readby`
This commit is contained in:
luzpaz 2021-07-08 07:38:13 -04:00 • committed by GitHub
parent bc6f060b8c
commit e0296b6a6d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
87 changed files with 132 additions and 132 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/content/doc/help/faq.en-us.md
View file

@ -142,7 +142,7 @@ The current way to achieve this is to create/modify a user with a max repo creat
Restricted users are limited to a subset of the content based on their organization/team memberships and collaborations, ignoring the public flag on organizations/repos etc.\_\_
Example use case: A company runs a Gitea instance that requires login. Most repos are public (accessible/browseable by all co-workers).
Example use case: A company runs a Gitea instance that requires login. Most repos are public (accessible/browsable by all co-workers).
At some point, a customer or third party needs access to a specific repo and only that repo. Making such a customer account restricted and granting any needed access using team membership(s) and/or collaboration(s) is a simple way to achieve that without the need to make everything private.