Clarify where the artifacts metadata .gz is generated

7b0ca61f · Eric Eastwood · 8921af39 · 7b0ca61f
Commit 7b0ca61f authored Oct 05, 2017 by Eric Eastwood
Show whitespace changes
Inline Side-by-side

Showing with 3 additions and 3 deletions

doc/administration/job_artifacts.md doc/administration/job_artifacts.md +3 -3

No files found.
--- a/doc/administration/job_artifacts.md
+++ b/doc/administration/job_artifacts.md
@@ -142,9 +142,9 @@ and [projects APIs](../api/projects.md).
 ## Implementation details
 When GitLab receives an artifacts archive, an archive metadata file is also
-generated. This metadata file describes all the entries that are located in the
+generated by [GitLab Workhorse]. This metadata file describes all the entries
-artifacts archive itself. The metadata file is in a binary format, with
+that are located in the artifacts archive itself.
-additional GZIP compression.
+The metadata file is in a binary format, with additional GZIP compression.
 GitLab does not extract the artifacts archive in order to save space, memory
 and disk I/O. It instead inspects the metadata file which contains all the