docs: Improve clarity and formality of cleanup instruction

[mdqst]

Description

In the documentation for the cleanup process, the phrase "clean all" was used, which could be perceived as a bit too informal. To enhance clarity and professionalism, I’ve replaced it with "clean everything".

This minor change helps maintain a consistent tone throughout the documentation, ensuring instructions are clear and easily understood by all users.

• 📚 Examples / docs / tutorials / dependencies update
• 🔧 Bug fix (non-breaking change which fixes an issue)
• 🥂 Improvement (non-breaking change which improves an existing feature)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 🔐 Security fix

Checklist

• I've read the CODE_OF_CONDUCT.md document.
• I've read the CONTRIBUTING.md guide.
• I've updated the code style using make codestyle.
• I've written tests for all new methods and classes that I created.
• I've written the docstring in Google format for all the methods and classes that I used.

[sagar-a16z]

Thanks