Adding information about outdated information

Added a paragraph under `Documenting your processes` talking about the obsolescence of documentation.

Author: Igor Steinmacher

_articles/en-US/best-practices.md

@@ -35,6 +35,8 @@ Writing things down makes it easier to say no when something doesn't fit into yo
 
 Even if you don't use full paragraphs, jotting down bullet points is better than not writing at all.
 
+Dismissing outdated information or, at least, clearly identifying it as outdated is a good practice. By clearly pointing the absence or obsolescence of documents, communities can ask for help to update or create such documentation. 
+
 ### Write down your project's vision
 
 Start by writing down the goals of your project. Add them to your README, or create a separate file called VISION. If there are other artifacts that could help, like a project roadmap, make those public as well.