style: fix more typos in /docs/user

docs/user/actions.md

@@ -647,7 +647,7 @@ jobs:
     runs-on: docker
 ```
 
-means that the `Forgejo runner` that claims to provide a kind of machine labelled `docker` will be selected by `Forgejo` and sent the job to be run.
+means that the `Forgejo runner` that claims to provide a kind of machine labeled `docker` will be selected by `Forgejo` and sent the job to be run.
 
 The actual machine provided by the runner **entirely depends on how the `Forgejo runner` was registered** (see the [Forgejo Actions administrator guide](../../admin/actions/) for more information).
 

docs/user/merge-message-templates.md

@@ -37,4 +37,4 @@ You can use the following variables enclosed in `${}` inside these templates whi
 When rebasing without a merge commit, `REBASE_TEMPLATE.md` modifies the message of the last commit. The following additional variables are available in this template:
 
 - CommitTitle: Commit's title
-- CommitBody: Commits's body text
+- CommitBody: Commit's body text

docs/user/profile.md

@@ -22,7 +22,7 @@ Making the `.profile` repository private will hide the Profile README.
 Rather than supporting multiple social links on the profile card, under the user
 avatar, such links - including
 [`rel=me`](https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/rel/me)
-attributes - can be placed in the `.profile` readme instead. This gives a user a
+attributes - can be placed in the `.profile` README instead. This gives a user a
 lot of flexibility on how they wish to display these links. To add a `rel=me`
 attribute, the link should be written in HTML, rather than in Markdown format,
 for example: `<a rel="me"

docs/user/repo-mirror.md

@@ -28,7 +28,7 @@ For an existing remote repository, you can set up pull mirroring as follows:
 
 The repository now gets mirrored periodically from the remote repository. You can force a sync by selecting **Synchronize Now** in the repository settings.
 
-:exclamation::exclamation: **NOTE:** You can only set up pull mirroring for repos that don't exist yet on your instance. Once the repo is created, you can't convert it into a pull mirror anymore. :exclamation::exclamation:
+:exclamation::exclamation: **NOTE:** You can only set up pull mirroring for repositories that don't exist yet on your instance. Once the repository is created, you can't convert it into a pull mirror anymore. :exclamation::exclamation:
 
 ## Pushing to a remote repository
 

docs/user/repo-permissions.md

@@ -6,7 +6,7 @@ origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/85d333f48bad
 
 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.
 
-You can assign teams different levels of permission for each unit (e.g. issues, PR's, wiki).
+You can assign teams different levels of permission for each unit (e.g. issues, PRs, wiki).
 
 ## Profile and Visibility
 

docs/user/versions.md

@@ -23,7 +23,7 @@ and they match what is displayed by the CLI or the web UI.
 
 ## Compatibility with Gitea
 
-As of Forgejeo 7.0.0 tools designed to work with Gitea 1.22.0 and
+As of Forgejo 7.0.0 tools designed to work with Gitea 1.22.0 and
 below are compatible and do not need any modification to keep working.
 
 In the future, if a tool wants to assert the level of compatibility of

docs/user/webhooks.md

@@ -119,7 +119,7 @@ X-Gitea-Event: push
 
 ### Example
 
-This is an example of how to use webhooks to run a php script upon push requests to the repository.
+This is an example of how to use webhooks to run a PHP script upon push requests to the repository.
 In your repository Settings, under Webhooks, Setup a Forgejo webhook as follows:
 
 - Target URL: http://example.com/webhook.php
@@ -129,7 +129,7 @@ In your repository Settings, under Webhooks, Setup a Forgejo webhook as follows:
 - Trigger On: Push Events
 - Active: Checked
 
-Now on your server create the php file webhook.php
+Now on your server create the PHP file webhook.php
 
 ```
 <?php

docs/user/wiki.md

@@ -5,7 +5,7 @@ origin_url: 'https://codeberg.org/Codeberg/Documentation/src/commit/85d333f48bad
 ---
 
 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.  
-Codeberg allows you to add a wiki to a repo for additional documentation.
+Codeberg allows you to add a wiki to a repository for additional documentation.
 
 The user in these examples is `knut`, the polar bear and its repository is `foobar`.
 
@@ -23,7 +23,7 @@ To edit the wiki `write` permission to the repository is required, unless the `A
 
 ## Wiki structure
 
-The wiki is essentially a separate Git repo in your repository with a predefined name in the form of `<your-repository-name>.wiki.git`.
+The wiki is essentially a separate Git repository in your repository with a predefined name in the form of `<your-repository-name>.wiki.git`.
 
 It consists of [Markdown](https://en.wikipedia.org/wiki/Markdown) files (file extension `.md`) and additional assets like images.  
 No further stylesheets are needed. The Markdown files are automatically rendered according to the selected Forgejo theme.
@@ -40,7 +40,7 @@ Clicking on the "Insert Image" button will make the following text appear in you
 
 ## Adding content using a local Git client
 
-You can work with the wiki repo as you would with any other Git repo on Forgejo.
+You can work with the wiki repository as you would with any other Git repository on Forgejo.
 
 ```shell
 git clone git@codeberg.org:knut/foobar.wiki.git