<!--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=350696) </details> <!--IssueSummary end--> I don't think it's entirely clear to users that applying a suggestion creates a commit in the repository. There may be unintended consequences from that lack of understanding. For example, a commit triggers a pipeline, which a user may not want to happen. They may be confused at the number of commits, thinking they'd only made one, the initial commit. A commit is a basic Git concept, and linking these more closely with applying a suggestion may make it easier for users to understand. **Proposal** - Change `Apply suggestion` to `Commit suggestion`. The text `Add suggestion to batch` should remain unchanged. - Change the `Applied` button that appears when a suggestion has been applied to `Committed`.