Cloudron docs riddled with egregious spelling and grammar errors
-
I suggest you pay a freelancer on Fiverr.com to proofread https://docs.cloudron.io/ because they are riddled with egregious spelling and grammar errors. For example...
dis no look vry proofesional.
Does it?
Pro tip: Spellcheckers are a thing. Use them when creating verbiage that will be customer-facing!
whn u chats wiz ur frends, speling annd gramar nott soo importunt.
But if you want people to pay you $180 per year to use Cloudron, well, ummm, yeah... break out that spiffy little spellchecker you've got gathering dust in your closet (/sarcasm) and pay a native speaker to proofread your text.
-
Ha ha, fair criticism. Most of the docs are written by me and I and not a native speaker. I copy/pasted the docs into some grammar websites and they did find some obvious typos. I will try to get them fixed over the week.
If you are interested in helping, our docs are at https://git.cloudron.io/cloudron/docs.
-
@girish I am sorry but I am not interested proofreading https://git.cloudron.io/cloudron/docs.
I repeat: I suggest you pay a freelancer on Fiverr.com to proofread https://git.cloudron.io/cloudron/docs.
I suggest you contact a dozen or so freelancers on Fiverr.com. (By the way, they are referred to as "sellers" not "freelancers" on Fiverr.com). I suggest you ask them simply, "How much would you charge to proofread/clean up https://git.cloudron.io/cloudron/docs?"
I would guess you would need to pay, say, 10 US dollars to 20 US dollars to each freelance proofreader whom you were to engage. I suppose a native speaker who enjoys and is good at proofreading, would need to spend approximately an hour to complete the task properly.
However, you might need to test out several freelancer proofreaders before you find one you like. I guess the project might cost you guys somewhere around 60 US dollars for three freelance proofreaders instead of, say, around 50 US dollars, because, if I am not mistaken, Fiverr would charge you a 20% fee.
However, once you find a freelancer you like, you'd probably be able to work with that person on an ongoing basis because I assume proofreading/editing text on cloudron.io would be easy work for a native speaker who enjoys that sort of work.
Like most startups, cloudron.io will probably fail. To increase your chances of success you guys need... 2b sur yur websight luks proofesional.
Because you are a non-native speaker—who I presume is an engineer—frankly, you'll probably never be a good writer in the English language. But well, hmmm... at the end of the day: who cares? None of us are good at everything; to earn money we only need to be good at something marketable!
-
@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.
-
@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/
-
@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.
-
@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.
-
-
@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? -
@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.
