Improve English and writing style of README.md

[Copilot]

This PR improves the English and writing style of the README.md file to make it more professional, natural, and consistent with serious open-source GitHub projects.

Changes Made

The improvements focus on grammar, clarity, and consistency while preserving all original technical content:

Grammar and Spelling

• Fixed spelling errors (e.g., "identifiant" → "identifier", "excution" → "execution", "immediatly" → "immediately")
• Corrected inconsistent capitalization (e.g., "yaml" → "YAML")
• Fixed typos throughout the document

Improved Clarity

• Enhanced sentence structure for better readability

  • Before: "PIMO is a tool for data masking. It can mask data from a JSONline stream and return another JSONline stream thanks to a masking configuration"
  • After: "PIMO is a tool for data masking. It can mask data from a JSONline stream and return another JSONline stream using a masking configuration"

• Clarified technical descriptions

  • Before: "generated data is not distinguishable from real data"
  • After: "generated data is indistinguishable from real data"

• Standardized terminology

  • Before: "The different URI usable with this selector are : pimo, file and http/https"
  • After: "The different URI schemes supported by this selector are: pimo, file, and http/https"

Enhanced Consistency

• Standardized punctuation (e.g., consistent use of colons, commas in lists)
• Improved list formatting throughout
• Made terminology consistent across all sections
• Standardized technical references

Professional Tone

• Removed casual language
• Made instructions more direct and clear
• Improved flow and readability for native English speakers

What Was Preserved

• ✅ All technical content and meaning
• ✅ All code examples and configurations
• ✅ All section structures and organization
• ✅ All links, badges, and references
• ✅ All Markdown formatting

Statistics

• 194 insertions, 195 deletions
• All major sections improved: introduction, configuration, usage, masks, advanced features, and final sections
• Zero changes to functionality or technical accuracy

The README now provides a better reading experience while maintaining all the valuable technical information that makes PIMO a powerful data masking tool.

Original prompt

Improve the English and writing style of the README file without changing its meaning or technical content. The goal is to make it sound natural, professional, and consistent with the tone and formatting commonly found in serious open-source GitHub projects.

Requirements:

• Fix grammar, spelling, and awkward phrasing.
• Keep all original information and structure.
• Do not add new content or modify the technical meaning.
• Use concise and fluent English that feels natural to native speakers.

Maintain Markdown formatting and section titles.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.