versioning: Switch to the apertisX packaging suffix

The Apertis packaging toolchain and pipelines have switched from the
`coX` packaging version suffix to `apertisX` to better distinguish the
work of the Apertis team from more Collabora-specific packages.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

content/architecture/versioning.md

@@ -55,9 +55,9 @@ how should we version the package if we want to apply some changes on top of
 Debian package?  The convention, when modifying the package for security
 updates, backports and downstream modification, is to append to the end of the
 existing Debian version number. As a result of this policy, packages in
-Apertis bear the addition `coX`, where `X` is a incremented number, which
-shows the number of modifications made to the package by Collabora for Apertis.
-The `co0` suffix means that the only difference between the upstream package
+Apertis bear the addition `apertisX`, where `X` is a incremented number, which
+shows the number of modifications made to the package by the Apertis team.
+The `apertis0` suffix means that the only difference between the upstream package
 from Debian and the package in Apertis is the metadata under `debian/apertis/`
 and the changelog entry itself. This is to highlight the fact that this metadata
 ends up in the generated source package, so this source package carries a
@@ -65,8 +65,8 @@ small delta against the corresponding Debian package.
 
 Additionally, there are a number of symbols that are used to separate these
 portions of the revision.  The symbol `~` is used to infer "less", and `+` for
-"more". For example, `1.0-1+co1` is considered greater than `1.0-1`, but
-`1.0-1~co1` is lower version than `1.0-1`. This ensures that we don’t end up
+"more". For example, `1.0-1+apertis1` is considered greater than `1.0-1`, but
+`1.0-1~apertis1` is lower version than `1.0-1`. This ensures that we don’t end up
 creating packages whose versioning collides with later upstream versioning and
 allows us to control which package is preferred over another by the package
 manager which ulitimately uses the version/revision string to decide which
@@ -82,11 +82,11 @@ Further examples:
   - Binary rebuild of the second revision of Debian’s packaging for the
     upstream `1.0` release.
   - No changes to the source.
-- `1.0-2co1`:
-  - Modification `1` by Collabora
+- `1.0-2apertis1`:
+  - Modification `1` by the Apertis team
   - Applied to the second revision of Debian’s packaging for the upstream `1.0`
     release.
-- `1.0-2ubuntu3co4foo5`:
+- `1.0-2ubuntu3apertis4foo5`:
   - Foo modification revision `5`
   - Using the Apertis modification revision `4`
   - Based on Ubuntu's modification revision `3`
@@ -102,8 +102,8 @@ Further examples:
 
 If in doubt, we can check on the command line:
 
-    $ dpkg --compare-versions 1.0-1+co1 gt 1.0-1 && echo YES
-    $ dpkg --compare-versions 1.0-1~co1 lt 1.0-1 && echo YES
+    $ dpkg --compare-versions 1.0-1+apertis1 gt 1.0-1 && echo YES
+    $ dpkg --compare-versions 1.0-1~apertis1 lt 1.0-1 && echo YES
 
 Here `gt` stands for “greater than”, while `lt` means “less than”.