sync with Codeberg 7bb8fa5ca559073c028805888195ee31b1f3d9c2

https://codeberg.org/Codeberg/Documentation

git diff 77bfb6cc15d180d506881e9629e73d1064c11dda..7bb8fa5ca559073c028805888195ee31b1f3d9c2 > doc.patch

(cherry picked from commit 89c24509f0)

docs/user/email-settings.md

@@ -1,7 +1,7 @@
 ---
 title: 'Email Settings'
 license: 'CC-BY-SA-4.0'
-origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/5d457efc069b52d512632fea024917e0848346cd/content/getting-started/email-settings.md'
+origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/7bb8fa5ca559073c028805888195ee31b1f3d9c2/content/getting-started/email-settings.md'
 ---
 
 By default, Forgejo will send notifications to your registered email addresses.

docs/user/first-repository.md

@@ -1,7 +1,7 @@
 ---
 title: Your First Repository
 license: 'CC-BY-SA-4.0'
-origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/5d457efc069b52d512632fea024917e0848346cd/content/getting-started/first-repository.md'
+origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/7bb8fa5ca559073c028805888195ee31b1f3d9c2/content/getting-started/first-repository.md'
 ---
 
 Almost everything on Forgejo happens in a repository. Think of a repository as a home for your project, where all of its source code can be organized using Git, as well as where you can track issues and read and write wikis.

docs/user/issue-tracking-basics.md

@@ -1,7 +1,7 @@
 ---
 title: 'The Basics of Issue Tracking'
 license: 'CC-BY-SA-4.0'
-origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/5d457efc069b52d512632fea024917e0848346cd/content/getting-started/issue-tracking-basics.md'
+origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/7bb8fa5ca559073c028805888195ee31b1f3d9c2/content/getting-started/issue-tracking-basics.md'
 ---
 
 Issues are an important mean of communication on Forgejo.

docs/user/repo-permissions.md

@@ -1,7 +1,7 @@
 ---
 title: 'Repository Permissions'
 license: 'CC-BY-SA-4.0'
-origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/5d457efc069b52d512632fea024917e0848346cd/content/collaborating/repo-permissions.md'
+origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/7bb8fa5ca559073c028805888195ee31b1f3d9c2/content/collaborating/repo-permissions.md'
 ---
 
 When you invite collaborators to join your repository or when you create teams for your organization, you have to decide what each collaborator/team is allowed to do.
@@ -10,16 +10,21 @@ You can assign teams different levels of permission for each unit (e.g. issues,
 
 ## Profile and Visibility
 
-Visibility of your repositories is in general inherited from your profile. So other user can only see your repositories, if your profile is _public_.
+The visibility of your repositories will depend on the visibility of your profile, as well as whether you have marked a repository as private. Let's break down what this means:
 
-If you want to limit visibility access to your repositories you can set your **user visibility** in the user privacy settings to **Limited**. Even if your repository is public, non-contributors will get a 404-error if they try to access your repository.
+- If your profile's visibility is set to "Limited", _all_ of your non-private repositories will only be visible to logged in users.
+- If your profile's visibility is set to "Public", _all_ of your non-private repositories will be shown to everyone.
+- If you do not want anyone (apart from your fellow collaborators) to see your repositories, mark your repository as "Private".
+
+The visibility of your profile can be changed in the `Privacy settings`. Be careful when you set your profile's visibility to "Limited"; Even if a repository is public, users that are _not logged in_ will get a [404 error](https://en.wikipedia.org/wiki/HTTP_404) if they try to access your repository — it will seem as if it does not exist at all!
 
 ![screenshot showing the updated README](../_images/user/repo-permissions/user-settings-privacy-limited.webp)
 
 ## Collaborators
 
-There are four permission levels: Read, Write, Administrator and Owner.  
+There are four permission levels: **Read**, **Write**, **Administrator** and **Owner**.
-The owner is the person who created the repository.
+
+By default, the person who creates a repository is an **_Owner_**.
 
 The table below gives an overview of what collaborators are allowed to do when granted each of these permission levels:
 
@@ -139,4 +144,4 @@ There are also two units which can be toggled:
 - External Wiki: access to external wiki.
 - External Issues: access to the external issue tracker.
 
-A team can be given the permission to create new repositories. When a member of such team creates a new repository, he/she will get administrator access to the repository.
+A team can be given the permission to create new repositories. When a member of such team creates a new repository, they will get administrator access to the repository.

docs/user/wiki.md

@@ -1,7 +1,7 @@
 ---
 title: 'Integrated Wiki'
 license: 'CC-BY-SA-4.0'
-origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/5d457efc069b52d512632fea024917e0848346cd/content/getting-started/wiki.md'
+origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/7bb8fa5ca559073c028805888195ee31b1f3d9c2/content/getting-started/wiki.md'
 ---
 
 A [wiki](https://en.wikipedia.org/wiki/Wiki) is a collaborative space on the web. It is a common practice to use wikis to collect knowledge and share information.