Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

50%
+0 −0
Q&A How can I write a review?

You can't be one hundred percent sure that you don't have any mistakes in your writing. It's the same as with testing a program - you can find bugs and be certain that a version therefore has flaws...

posted 6y ago by Secespitus‭  ·  last activity 4y ago by System‭

Answer
#4: Attribution notice removed by user avatar System‭ · 2019-12-12T23:01:22Z (over 4 years ago)
Source: https://writers.stackexchange.com/a/35096
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#3: Attribution notice added by user avatar System‭ · 2019-12-08T08:32:36Z (over 4 years ago)
Source: https://writers.stackexchange.com/a/35096
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision by (deleted user) · 2019-12-08T08:32:36Z (over 4 years ago)
You can't be one hundred percent sure that you don't have any mistakes in your writing. It's the same as with testing a program - you can find bugs and be certain that a version therefore has flaws, but there will almost always be things you just can't test, because you don't have the time to fully check every little detail in a project of a significant size.

There are many tools that can help you, such as the basic spellcheckers that programs like Microsoft Word have already included. They will be able to pick up a lot of common mistakes and make you aware of them. But there will always be edge cases where these spellcheckers are simply wrong. See [Knowing when to disobey the advice of grammar software](https://writing.stackexchange.com/q/33326/23159) for more information about this topic.

You can also give your draft to someone that regularly checks writing for mistakes. Professional editors can help you a lot. See [Where do I go looking for an editor?](https://writing.stackexchange.com/q/32157/23159) and [How do I find an affordable editor?](https://writing.stackexchange.com/q/2529/23159) for more information.

You can also write something and then let it sit for a couple of days or weeks while working on something different. You will more easily pick up the problems in your writing if you are not so close to your writing anymore, because you are routine-blinded when reading the same thing over and over. See for example [this answer to _So I finished my novel. Now what do I do?_](https://writing.stackexchange.com/a/3993/23159) for more information. This advice works better if it's a longer project that you are working on where you can simply _take a few days off_.

For a general tips collection on making _fewer_ mistakes (as opposed to _none_ that you are aiming for) you might want to look at [How can I catch more errors when I proofread?](https://writing.stackexchange.com/q/5400/23159)

#1: Imported from external source by user avatar System‭ · 2018-04-16T10:55:34Z (about 6 years ago)
Original score: 3