Edit new configuration settings documentation

doc/user/admin_area/settings/continuous_integration.md

@@ -29,26 +29,30 @@ If you want to disable it for a specific project, you can do so in
 ## Maximum artifacts size **(CORE ONLY)**
 
 The maximum size of the [job artifacts](../../../administration/job_artifacts.md)
-can be set at the project level, group level, and at the instance level. The value is in *MB* and
-the default is 100MB per job; on GitLab.com it's [set to 1G](../../gitlab_com/index.md#gitlab-cicd).
+can be set at the project level, group level, and at the instance level. The value is:
 
-To change it at the instance level:
+- In *MB* and the default is 100MB per job.
+- [Set to 1G](../../gitlab_com/index.md#gitlab-cicd) on GitLab.com.
 
-1. Go to **Admin area > Settings > Continuous Integration and Deployment**.
-1. Change the value of maximum artifacts size (in MB).
-1. Hit **Save changes** for the changes to take effect.
+To change it at the:
 
-at the group level (this will override the instance setting):
+- Instance level:
 
-1. Go to **Group > Settings > CI / CD > General Pipelines**.
-1. Change the value of maximum artifacts size (in MB).
-1. Hit **Save changes** for the changes to take effect.
+   1. Go to **Admin area > Settings > Continuous Integration and Deployment**.
+   1. Change the value of maximum artifacts size (in MB).
+   1. Hit **Save changes** for the changes to take effect.
 
-at the project level (this will override the instance and group settings):
+- [Group level](../../group/index.md#group-settings) (this will override the instance setting):
 
-1. Go to **Project > Settings > CI / CD > General Pipelines**.
-1. Change the value of maximum artifacts size (in MB).
-1. Hit **Save changes** for the changes to take effect.
+  1. Go to the group's **Settings > CI / CD > General Pipelines**.
+  1. Change the value of **maximum artifacts size (in MB)**.
+  1. Press **Save changes** for the changes to take effect.
+
+- [Project level](../../project/pipelines/settings.md) (this will override the instance and group settings):
+
+  1. Go to the project's **Settings > CI / CD > General Pipelines**.
+  1. Change the value of **maximum artifacts size (in MB)**.
+  1. Press **Save changes** for the changes to take effect.
 
 ## Default artifacts expiration **(CORE ONLY)**
 

doc/user/group/index.md

@@ -451,6 +451,11 @@ For performance reasons, we may delay the update up to 1 hour and 30 minutes.
 
 If your namespace shows `N/A` as the total storage usage, you can trigger a recalculation by pushing a commit to any project in that namespace.
 
+### Maximum artifacts size **(CORE ONLY)**
+
+For information about setting a maximum artifact size for a group, see
+[Maximum artifacts size](../admin_area/settings/continuous_integration.md#maximum-artifacts-size-core-only).
+
 ## User contribution analysis **(STARTER)**
 
 With [GitLab Contribution Analytics](contribution_analytics/index.md),

doc/user/project/pipelines/settings.md

@@ -60,6 +60,11 @@ if the job surpasses the threshold, it is marked as failed.
 Project defined timeout (either specific timeout set by user or the default
 60 minutes timeout) may be [overridden on Runner level](../../../ci/runners/README.html#setting-maximum-job-timeout-for-a-runner).
 
+## Maximum artifacts size **(CORE ONLY)**
+
+For information about setting a maximum artifact size for a project, see
+[Maximum artifacts size](../../admin_area/settings/continuous_integration.md#maximum-artifacts-size-core-only).
+
 ## Custom CI config path
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/12509) in GitLab 9.4.