[docs] Improve formatting of the system

[oliviertassinari]

These changes help make the point that the sx prop allows a denser vertical spacing. They don't introduce a scrollbar in the docs. They would if I had use 100 or more.

---

#23294 was slightly rushed. I'm aware of 3 other follow-up changes that are coming:

• @mbrookes that was planning to revamp the wordings
• @mnajdova that was planning to act on the feedback to improve the description of /system/properties/
• The need to remove the orphan demos.

[mui-pr-bot]

Details of bundle changes

Generated by 🚫 dangerJS against e7ad1bc

[mnajdova]

Looks much better 👍

[eps1lon]

#23294 was slightly rushed.

Moving fast requires actions not words. The follow-up was announced so I have no idea what the problem is now. We're not deploying on merge anyway.

Funnily enough a 17 day open PR is considered "rushed" but your 11 hour open on is not. The "consistency" you always strive for should be applied to your own work first before demanding it of other collaborators.

The character width is not just chosen because we felt funny but because it's tied to the documentation styles. Any change should be applied to all pages. Formatting only lives from consistency.

[oliviertassinari]

Moving fast requires actions not words. The follow-up was announced so I have no idea what the problem is now. We're not deploying on merge anyway.

Yeah, we had to unlock it at some point, we can't make each pull-request perfect, never going to happen nor should we aim for it, it's about the good enough. I was more interested in listing the follow-ups that can help.

---

The character width is not just chosen because we felt funny but because it's tied to the documentation styles. Any change should be applied to all pages. Formatting only lives from consistency.

There are two different use-cases:

1. See a completing demo that wants to make me use the module. A developer wants it to go to the point, see the potential.
2. Read the docs, the API for a module I need to use. A developer doesn't want to scroll to find important information.

I think that it's completely fine to have two different formating configurations for 1. and 2., the user-journey and expectations are different. It's always about how easy a developer can process the information and how can the formatting help.