Closed jamesmbaazam closed 3 weeks ago
Thanks @jamesmbaazam for opening an issue - could you please add a example of the current language and the proposed one? This helps clarity on what you mean for those not as familiar with the grammar rules (my brain cannot parse grammar rules in any language for some reason 😅).
Sure.
Two examples that currently align with my suggestion are:
others that can be aligned (not exhaustive):
package | Current description | Proposed change |
---|---|---|
readepi | Tools for reading data | Import data |
cleanepi | Tools for cleaning data | Clean imported data |
ColOpenData | Open data for Colombia | ¯_(ツ)_/¯ |
linelist | Tagging and validating individual data | Tag and validate individual data |
I can submit a PR if that will make your life easier 😄 .
maybe there's a Chesterton fence
As an aside, I really like this. I'm adding it to my collection of mental models.
No reason. The text here was written during the early quick prototyping phase and I have no objections for it to be updated.
maybe there's a Chesterton fence
As an aside, I really like this. I'm adding it to my collection of mental models.
@chartgerink I'm so sorry I mistakenly deleted your original comment that I was quoting 😠. If it's not too much trouble, could you repost it?
I just noticed that the package descriptions on the hex wall have a mix of tenses and could be standardized. The imperative tense would read more nicely, so I would suggest changing the descriptions of
{readepi}
,{cleanepi}
,{epichains}
, etc., to align with the others that already use that tense.