Update prototyping-utilities.md

[chrisdfe]

Description

Removed an unnecessary apostrophe in the description there.

Types of changes

• Documentation
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (anything that would change an existing functionality)
• Maintenance (refactor, code cleaning, development tools...)

Checklist

• I have read and follow the CONTRIBUTING.md document.
• The pull request title and template are correctly filled.
• The pull request targets the right branch (develop or develop-v...).
• My commits are correctly titled and contain all relevant information.
• I have updated the documentation accordingly to my changes (if relevant).
• I have added tests to cover my changes (if relevant).

[ncoden]

Hi @chrisdfe 👋,

I have an idea about what the whole sentence should mean, but "into hi-fi coded prototypes ultra fast." look like words were put in the wrong order.

I am missing something? I'm not a native english speaker.

[chrisdfe]

Hi @ncoden!
I see what you mean - that whole sentence is a little confusing. The apostrophe in "prototypes" was definitely incorrect grammar though.

Do you think this reads any better?
"These optional classes and mixins are great for quickly turning sketches and mockups into hi-fi coded prototypes."

[ncoden]

@chrisdfe Yes this is way better, thank you! Could you provide a commit for this?

[chrisdfe]

👍

[SassNinja]

I'm not an English native speaker either but the hi-fi sounds really weird to me.
I would just write and mockups into coded prototypes.