Document worker publication

Closes #254 (closed)

docs/contents/workers/publication.md

@@ -6,7 +6,7 @@ While workers may be [run locally](./run-local.md), they are usually written to
 
 ## How it works
 
-The template implements a new CI job, `publish-worker`, at the last stage of the pipeline. When every job of the previous stages have passed, this one will try to publish a new version, using the newly built Docker image, on every Arkindex instance specified by the `ARKINDEX_INSTANCE` variable. The publication is done using the [Arkindex CLI tool](<https://cli.arkindex.org/workers/#publish-workers>).
+The template implements a new CI job, `publish-worker`, at the last stage of the pipeline. When every job of the previous stages have passed, this one will try to publish a new worker version, using the newly built Docker image, on every Arkindex instance specified by the `ARKINDEX_INSTANCE` variable. The publication is done using the [Arkindex CLI tool](<https://cli.arkindex.org/workers/#publish-workers>).
 
 !!! warning
 
@@ -14,7 +14,7 @@ The template implements a new CI job, `publish-worker`, at the last stage of the
 
 !!! note
 
-    If your repository defines multiple workers, one version will be pushed per worker. However, there will still only be one job per instance.
+    If your repository defines multiple workers, one worker version will be pushed per worker. However, there will still only be one job per instance.
 
 
 ## Authentication in CI
@@ -25,5 +25,5 @@ Since the publication is done during a GitLab CI, no optional arguments are [nee
 
 In the template, a publication to <https://demo.arkindex.org> (slug `demo`) is presented. To publish to another instance, make sure that:
 
-- the authentication credentials are present in the secure file,
+- the authentication credentials for that instance are present in the secure file,
 - the slug is listed as a potential value for `ARKINDEX_INSTANCE` in the `publish-worker` job configuration.