Fix wording fix

[garak]

See #411 (review)

[Copilot]

Pull Request Overview

This PR corrects a grammatical error in the documentation by fixing subject-verb agreement.

• Fixes grammatical error where "becomes" should be "become" to match the plural subject "menus"

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[garak]

I tried to rebase, yet a few irrelevant commits are shown in this PR. I'm confident they will be ignored after the merge (squash merging shouldn't be necessary)

[stof]

@garak those commits are not in the history of the master branch. We have similar commit messages but with different hashes:

you should use git rebase --onto master 47b4ec5bddef40c5fb5e0e01b15ff9f2d077a5b4 to rebase only your latest commit onto master instead of rebasing also the commit and its revert.

[garak]

you should use git rebase --onto master 47b4ec5bddef40c5fb5e0e01b15ff9f2d077a5b4 to rebase only your latest commit onto master instead of rebasing also the commit and its revert.

I followed your suggestion:

$ git rebase --onto master 47b4ec5
$ git push --force-with-lease

but the situation didn't improve

[stof]

Was your master branch up-to-date ?

[garak]

Was your master branch up-to-date ?

I found out that git fetch upstream && git merge upstream/master wasn't enough, so I reset my fork. Now it looks good.

[shakaran]

@stof could you merge this? Thanks