Cloudron docs riddled with egregious spelling and grammar errors

[girish]

@yeku thanks for the suggestion, will keep that in mind.

Like most startups, cloudron.io will probably fail.

For some background, we are not a startup and more like an indie software shop. We haven't taken any investment and our company growth and revenue goals are not like a startup. We have been around for over 5 years now and reasonably successful and have a net profit. In fact, we make enough to contribute to upstream projects now. TBH, if anything, we want to make more money, not for ourselves but to help other projects even more.

[yeku]

@girish Thanks for letting me know. I wish you well.

[scooke]

@girish I'm now curious about all these egregarious errors! So I'll take a look. You all have terrific attitude, btw. Keep up the good work.

[my1water]

@girish saw this on reddit after reading this thread: https://www.reddit.com/r/opensource/comments/pa2esx/english_grammar_checking_cl_tool_to_add_to_ci/

One of the suggested solutions looks decent: https://languagetool.org/

[ruihildt]

@my1water Language Tool could be packaged for Cloudron.

[girish]

@my1water ah, languagetool is indeed quite nice. I just installed their extension, let's see how it goes.

[scooke]

@my1water I have installed it, and tried it out on one of the Doc pages, but it didn't work and I received a 400 error. So, I went to the https://languagetool.org/ site and made an account. Then, I refreshed the page and voila! It does work, and it's suggestions were pretty good, too.

[marcusquinn]

@my1water I like the https://languagetool.org/ browser extensions, always worked well for me. Native English but always need these things due to constant hurry and not enough typing accuracy.

[robi]

@marcusquinn @scooke both of your links don't seem to go to the expected site..

UPDATE: @girish fixed your links to prevent the spread of malware by the typo'd domains. Thanks Girish

[bubonicfred]

@girish I tried to sign in to the git with both github and gitlab and failed cause of the non-approved email thing, which I thought was fixed?
I've recently installed language tool and I am enjoying it.
I've also used proselint in the past, which aims to improve writing with a low false alarm rate. http://proselint.com/
There's also https://github.com/btford/write-good which is aimed at developers (and probably a few others too)
I'm now curious if either of those can be implemented as tests for pull requests?

[scooke]

@robi Yikes! I was certain I typed in the correct url. Thanks for noticing. And thanks @girish for fixing them!

[timconsidine]

@yeku I understand the points, but I have only seen a couple of errors, and they haven't prevented me getting the message or successfully using Cloudron.

I think Cloudron have enough work running a fantastic architecture. The community here can help out @girish free of charge with great enthusiasm. Errors just need to be reported and they can be fixed quickly.