slight change in the wording just to make it easier to understand where
the token is placed.

I've also reworked a paragraph below. I don't see what's natural about
the limitations. They're just a random limitation that gitlab decided to
impose on the CE just so that they have more features for their paid
version.

service/documentation.md

@@ -198,7 +198,7 @@ To do this, you'll need to create [project access tokens](https://gitlab.torproj
 Wiki and use the [repository mirror feature](https://gitlab.torproject.org/help/user/project/repository/repository_mirroring.md) to replicate the wiki
 into a separate project.
 
- 1. in the Wiki project, head for the **Settings: Access Tokens** page
+ 1. in the project that contains the Wiki (for example tpo/tpa/team>), head for the **Settings: Access Tokens** page
     and create a new token:
     - name: `wiki-replica`
     - expiration date: removed
@@ -243,10 +243,10 @@ triggered. Refresh the page to see status, you should see the **Last
 successful update** column updated. When you push to the replica, the
 wiki should be updated.
 
-Naturally, because of limitations of GitLab, you cannot pull changes
-from the wiki to the replica. But considering only a limited set of
-users have access to the wiki in the first place, this shouldn't be a
-problem as long as everyone pushes to the replica.
+Because of limitations imposd on GitLab Community Edition, you cannot pull
+changes from the wiki to the replica. But considering only a limited set of
+users have access to the wiki in the first place, this shouldn't be a problem as
+long as everyone pushes to the replica.
 
 Another major caveat is that git repositories and wikis have a
 different "home page". In repositories, the `README.*` or `index.*`