diff --git a/.forgejo/workflows/pr.yml b/.forgejo/workflows/pr.yml
index e77e75b5..584e4b72 100644
--- a/.forgejo/workflows/pr.yml
+++ b/.forgejo/workflows/pr.yml
@@ -1,7 +1,7 @@
 name: pr
 
 on:
-  pull_request:
+  pull_request_target:
 
 jobs:
   preview:
diff --git a/README.md b/README.md
index 96ce9f7e..67f3eac2 100644
--- a/README.md
+++ b/README.md
@@ -116,23 +116,6 @@ Such a feature branch can then be merged into multiple versions of the docs if a
 In this case, the feature branch should usually be taken from the last common ancestor of all of the
 version branches into which it will potentially be merged.
 
-If you have commit access to this repository, you should work on a temporary branch within this repository
-with the `pr/` prefix and submit your pull request from there. Use the following commands to do it.
-
-```sh
-git clone git@codeberg.org:forgejo/docs ; cd docs
-git checkout <target-branch>
-git checkout -b pr/<short-pr-desc>
-# Make the changes you want to submit
-git add . ; git commit
-git push -u origin pr/<short-pr-desc>
-# Proceed to open your pull request
-```
-
-This is currently necessary due to technical limitations with Forgejo Actions. If you do not have commit
-access, you may fork this repository and send a pull request the usual way, but a live preview of the
-website will not be available.
-
 #### Backports
 
 If a PR is meant to be backported to a stable branch, it must be