README formatting fixes and new example

[erwinkramer]

Description

• formatting fixes in README
• new example

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• I have performed a self-review of my code
• I have added tests that prove my fix is effective or that my feature works
• I have made corresponding changes to the documentation
• I have commented my code, particularly in hard-to-understand areas
• New and existing unit tests pass locally with my changes

[what-the-diff]

PR Summary

• Cleaning Up the README File
  We have done some tidying up work in the README file, removing an unnecessary empty line in the badge section to make it more organized and readable.
• Improving Article Titles
  We have revised a heading in one of our articles, changing "Using Gridify in the api controllers" to "Using Gridify in API Controllers." for better comprehension.
• Adding New Reference Material
  We have supplemented our resources with a new reference article: "Bank API 🏦, a reference project which sets a standard for building a compliant and modern API," written by Erwin Kramer.
• Correcting Typos
  We have corrected a minor typing error, changing "Comming soon" to the correct "Coming soon."
• Enhancing Web Accessibility
  For better web accessibility, we have added an alt attribute to the contributors' image, which describes the content of the image for people who are visually impaired or choose not to load images. Improving accessibility will help us reach a broader audience with our project.

[alirezanet]

thanks 👌💐