diff --git a/docs/getting-started/gitlab.md b/docs/getting-started/gitlab.md
index 0bbc8e2..7f8ab75 100644
--- a/docs/getting-started/gitlab.md
+++ b/docs/getting-started/gitlab.md
@@ -12,7 +12,7 @@ See [Set up a hub's platform](../guide/setup.md#gitlab).
 
 1. **Create the hub.** Choose *New project → Import project → Repository by URL* and give
    the URL of [the template](https://github.com/bedrock-python/engineering-assets-template),
-   or fork its mirror at `gitlab.com/bedrock-python/engineering-assets-template`.
+   `https://github.com/bedrock-python/engineering-assets-template.git`.
 2. **Create two service accounts** and add them to the groups that own your
    repositories. On instances without service accounts, use group access tokens. Keep
    the hub out of those groups: put it in a group or subgroup the accounts don't belong
diff --git a/docs/project/release.md b/docs/project/release.md
index 78bdffb..835c068 100644
--- a/docs/project/release.md
+++ b/docs/project/release.md
@@ -141,7 +141,7 @@ Once, when the template is first published:
 
 - *Settings → General*: tick **Template repository**.
 - *Settings → Actions → General*: **Disable actions**. The template's workflows are a hub's: they deliver from the default branch and check every pull request of a hub, and in the template itself, with the placeholder `id` and no keys, every run would fail (`check` rejects the placeholder by design). touchmark's own CI checks the template instead (`ci.yml`, job `template`). Dependabot's version updates still open pull requests there.
-- The GitLab mirror `gitlab.com/bedrock-python/engineering-assets-template` that the template's README offers: create it, and turn **CI/CD** off in its *Settings → General → Visibility, project features, permissions*, for the same reason. Keep it in sync from outside the template: a workflow placed in the template is copied into every hub created from it.
+- A GitLab mirror `gitlab.com/bedrock-python/engineering-assets-template`: create it, and turn **CI/CD** off in its *Settings → General → Visibility, project features, permissions*, for the same reason. Keep it in sync from outside the template: a workflow placed in the template is copied into every hub created from it. Offer it in the template's README and in [GitLab](../getting-started/gitlab.md) only once it exists; until then both give the template's URL on GitHub to import.
 
 ## Try a release locally