<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=454607) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal Simplify the text. How? To be determined. ### Background There is a lot of text to read regarding the creation of a repository mirror From https://gitlab.com/gitlab-org/gitlab/-/issues/442380#note_1846913946 > This info box is quite full of words  Current text: - The repository must be accessible over http://, https://, ssh:// or git://. - When using the http:// or https:// protocols, please provide the exact URL to the repository. HTTP redirects will not be followed. - Do not include the username in the URL, use the username field below if required: https://gitlab.company.com/group/project.git. - When using the ssh:// protocol, please use the following format: ssh://username@example.com/group/project.git. - The update action will time out after 180 minutes. For big repositories, use a clone/push combination. - Git LFS objects will be synced if LFS is enabled for the project. Push mirrors will not sync LFS objects over SSH. - In case of pull mirroring, your user will be the author of all events in the activity feed that are the result of an update, like new branches being created or new commits being pushed to existing branches. <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->