Replace flowery language

[neofright]

A bouquet refers to trees or flowers. The etymology is pretty clear on the Latin root via French.

Seems a little pretentious?

Summary by Sourcery

Simplify wording by replacing flowery or pretentious terms throughout the project.

Enhancements:

• Remove French-derived or ornate vocabulary (e.g., 'bouquet') from project texts

Documentation:

• Update README content to use straightforward language

Tests:

• Revise example lyric file to eliminate overly ornate phrasing

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR simplifies documentation and sample lyrics by replacing the term “bouquet” with more straightforward alternatives to avoid pretentious language.

File-Level Changes

Change	Details	Files
Standardize terminology by replacing “bouquet” with simpler wording	Replaced “bouquet” with “bunch” in descriptive text Removed overly floral etymology notes Updated sample lyrics to reflect the new term	README.rst test/rsrc/lyrics/examplecom/beetssong.txt

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[semohr]

Thanks for the PR! LGMT

Fur the future: when applying changing the docs you need to run poe format-docs.

I rebased onto master and reformatted the docs for you.