[GSK-2807] Documentation polishing

[AbSsEnT]

Description

GSK-2806
GSK-2707
GSK-2767

Related Issue

Type of Change

• 📚 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

[linear]

GSK-2807 Documentation polishing

[luca-martial]

This doesnt need to be a different page

[AbSsEnT]

@luca-martial the contents was returned to its original place.

[luca-martial]

Ok looks good now - ill let @rabah-khalek review the rest since you addressed 3 different linear cards in 1 PR (better to separate next time)

[AbSsEnT]

@luca-martial yes, makes sense to me to separate in the future. However, since there were a lot of small issues dedicated to the same goal of the documentation polishing, I decided to submit everything at once. But yes, separation is good)

[Hartorn]

@luca-martial @rabah-khalek Can we merge this, or are we expecting changes ?

[Hartorn]

@AbSsEnT Btw, never redo the lockfile yourself, especially on MacOS : it's breaking the dependencies on Windows and other stuff. Either use label Lockfile on a PR, run the workflow on a branch, or use the pdm provided command running in docker ;)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud