another round of edits (team#40472)

policy/tpa-rfc-36-gitolite-gitweb-retirement.md

@@ -105,7 +105,7 @@ services will be shutdown and destroyed.
 
 ## Migration procedure
 
-Owners migrate their repositories using GitLab to import the
+Owners migrate their repositories using GitLab to [import][] the
 repositories from Gitolite. TPA then takes over and creates
 redirections on the Gitolite side, as detailed in the full [migration
 procedure][].
@@ -113,29 +113,30 @@ procedure][].
 Any given repository will have one of three state after the migration:
 
  * **migrated**: the repository is fully migrated from Gitolite to
-   GitLab
+   GitLab, redirections send users to GitLab and the repository is
+   active on GitLab
 
- * **archived**: the repository is migrated to GitLab but "archived",
-   keeping it from being changed in the future
+ * **archived**: like **migrated**, but "[archived][]" in GitLab,
+   which means the repository hidden in a different tab and immutable
 
- * **destroyed**: the repository is not worth migrating and will be
-   permanently destroy
+ * **destroyed**: the repository is not worth migrating at all and
+   will be permanently destroyed
 
 Unless requested otherwise in the next 9 months, TPA will *migrate*
 all remaining repositories.
 
 As of May 2023, no new repository may be created on Gitolite
-infrastructure, all new repositories MUST be created on GitLab. This
-is effectively the situation now anyways, TPA has not created a new
-Git repository in Gitolite in over two years.
+infrastructure, all new repositories MUST be created on GitLab.
+
+[archived]: https://docs.gitlab.com/ee/user/project/settings/#archive-a-project
+[import]: https://docs.gitlab.com/ee/user/project/import/
 
 ## Redirections
 
-Redirections for the web interfaces will be kept permanently in the
-static mirror system, for backwards compatibility. This will included
-a limited set of URLs that GitLab can support in a meaningful way. It
-will *not* include an SSH endpoint, which will start completely
-failing at the end of the migration.
+For backwards compatibility, web redirections will permanently set in
+the static mirror system. This will included a limited set of URLs
+that GitLab can support in a meaningful way. It will *not* include an
+SSH endpoint, which will start failing at the end of the migration.
 
 ## Per-repository particularities