<!--

* Use this issue template for suggesting new docs or updates to existing docs.
  Note: Doc work as part of feature development is covered in the Feature Request template.
  
* For issues related to features of the docs.gitlab.com site, see
     https://gitlab.com/gitlab-com/gitlab-docs/issues/       

* For information about documentation content and process, see
     https://docs.gitlab.com/ee/development/documentation/ -->

### Type of issue

Add the relevant label:

- `docs:fix` - Correction or clarification needed.
- `docs:new` - New doc needed to cover a new topic or use case.
- `docs:improvement` - Improving an existing doc; e.g. adding a diagram, adding or rewording text, resolving redundancies, cross-linking, etc.
- `docs:revamp` - Review a page or group of pages in order to plan and implement major improvements/rewrites.
- `docs:other` - Anything else.
   
### Problem to solve

<!-- Include the following detail as necessary:
* What product or feature(s) affected?
* What docs or doc section affected? Include links or paths.
* Is there a problem with a specific document, or a feature/process that's not addressed sufficiently in docs?
* Any other ideas or requests?
-->

### Further details

<!--
* Any concepts, procedures, reference info we could add to make it easier to successfully use GitLab?
* Include use cases, benefits, and/or goals for this work.
* If adding content: What audience is it intended for? (What roles and scenarios?)
  For ideas, see personas at https://design.gitlab.com/research/personas or the persona labels at
  https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A
-->

### Proposal

<!-- Further specifics for how can we solve the problem. -->

### Who can address the issue

<!-- What if any special expertise is required to resolve this issue? -->

### Other links/references

<!-- E.g. related GitLab issues/MRs -->

/label ~Documentation