<!--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=8795) </details> <!--IssueSummary end--> For https://docs.gitlab.com/ee/user/project/file_lock.html Currently, we have this note far down the page: > Note: Locking only works for the default branch you have set in the project's settings (usually master). Should this be mentioned sooner -- in the Overview? Should the note instead clarify that (per @northrup): > Locking a file does not prevent pulls, nor does it prevent other branches from uploading the file, it just prevents the file from being written in the branch it was locked in*. Typically this is the `master` branch of the project that all work is being merged into. * We could reword this one bit so it's not ambiguous: you can only lock files in one branch, your default branch, which is usually master.