Better proof reading
-
I'm not native english speaking. Which means that my english is far from perfect. A couple of years ago when I wrote articles you were very good at proof reading and fixing my grammar errors. I used to wait for an edit and then check the diff to see which errors I've made and learn from them. I've written three articles in a short time. And it doesn't seem like you proof read at all now. And that's sad imho. That was one of the best things with writing articles here. I could trust you to help me improve my articles (and let me learn thanks to that). Please read articles more carefully before you publish them. Especially if someone writes "please proof read" in the editor comment box.
-
I'm not native english speaking. Which means that my english is far from perfect. A couple of years ago when I wrote articles you were very good at proof reading and fixing my grammar errors. I used to wait for an edit and then check the diff to see which errors I've made and learn from them. I've written three articles in a short time. And it doesn't seem like you proof read at all now. And that's sad imho. That was one of the best things with writing articles here. I could trust you to help me improve my articles (and let me learn thanks to that). Please read articles more carefully before you publish them. Especially if someone writes "please proof read" in the editor comment box.
If English is not your native language then I would say your writing is remarkable, considering. Which article in particular are you looking at?
Thanks, Sean Ewington The Code Project
-
If English is not your native language then I would say your writing is remarkable, considering. Which article in particular are you looking at?
Thanks, Sean Ewington The Code Project
For instance these: Localization in ASP.NET MVC with Griffin.MvcContrib[^] Get injected into the world of inverted dependencies[^] The only edits were to fix the syntax highlighting (when the article was approved). I've re-read them several time to fix spelling errors and to try to fix malformed sentences (after the approval).
-
For instance these: Localization in ASP.NET MVC with Griffin.MvcContrib[^] Get injected into the world of inverted dependencies[^] The only edits were to fix the syntax highlighting (when the article was approved). I've re-read them several time to fix spelling errors and to try to fix malformed sentences (after the approval).
I think you have a strong grasp of spelling and grammar. I've gone ahead and finely combed these over, but I'd be happy to go more in depth with the proofreading of your articles if you'd like. Feel free to email me about any changes to your articles (now or later) and I'd be happy to go over the changes/additions I applied and why. Some of it is preference (I find commas in particular to be individual taste) but I'm happy to explore the "why" of all the changes if you would find that helpful.
Thanks, Sean Ewington The Code Project
-
I think you have a strong grasp of spelling and grammar. I've gone ahead and finely combed these over, but I'd be happy to go more in depth with the proofreading of your articles if you'd like. Feel free to email me about any changes to your articles (now or later) and I'd be happy to go over the changes/additions I applied and why. Some of it is preference (I find commas in particular to be individual taste) but I'm happy to explore the "why" of all the changes if you would find that helpful.
Thanks, Sean Ewington The Code Project
I believe email links require a "mailto:" to be prefixed to the URL for them to work*. The current link you created makes it look as if there's a forum dedicated entirely to your email. :) *Though, I wouldn't recommend putting your email on a public forum at all (especially not in plain text form).
-
I believe email links require a "mailto:" to be prefixed to the URL for them to work*. The current link you created makes it look as if there's a forum dedicated entirely to your email. :) *Though, I wouldn't recommend putting your email on a public forum at all (especially not in plain text form).
Drat. :-O Thanks for the catch.
Thanks, Sean Ewington The Code Project
-
I'm not native english speaking. Which means that my english is far from perfect. A couple of years ago when I wrote articles you were very good at proof reading and fixing my grammar errors. I used to wait for an edit and then check the diff to see which errors I've made and learn from them. I've written three articles in a short time. And it doesn't seem like you proof read at all now. And that's sad imho. That was one of the best things with writing articles here. I could trust you to help me improve my articles (and let me learn thanks to that). Please read articles more carefully before you publish them. Especially if someone writes "please proof read" in the editor comment box.
I don't think either of those articles were actually "edited" - they were just "approved". And perhaps while approving, some quick HTML fixes may have been done. In the old days, an article would show as unedited, and most editors would often make quick fixes and leave it unedited. They'd only mark it as edited once they did a full proof-read/editing on it. But with the new system, there's no such "unedited" status any more and this may be what's confusing.
Regards, Nish
My technology blog: voidnish.wordpress.com