- From: Kaelig Deloumeau-Prigent via GitHub <sysbot+gh@w3.org>
- Date: Fri, 17 Sep 2021 23:19:01 +0000
- To: public-design-tokens-log@w3.org
Cross posting my comment in the PR above (https://github.com/design-tokens/community-group/pull/76#issuecomment-922128207) here – note that I'm a frequent user of both Hemingway and Grammarly, and encourage editors to use them. --- I agree with the intent, but think an over-reliance on Hemingway is detrimental to the readability and clarity of this doc. I find that following Hemingway's suggestions too closely leads to a succession of tiny sentences that can read as quite dry, and breaks the flow of otherwise very readable content. In one of the sentences, all jargon was removed in an undesirable lossy rewrite. My guidance is to use Hemingway sparingly, and take its suggestions for what they are: suggestions. 👍🏻 It's useful to avoid very long sentences, repetitions, and spot passive voice that would read better as active. 👎🏻 It warns about jargon that's actually important in our context: technical reports are aimed at experts who rely on this vocabulary to derive precise meaning. --- (Grammarly allows to specify the target audience, tone, level of formality… I personally find it better than Hemingway for professional writing like technical proposals, and still use Hemingway for blog posts) -- GitHub Notification of comment by kaelig Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/66#issuecomment-922130012 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 17 September 2021 23:19:03 UTC