Merge pull request github#492 from infotexture/patch-1

Fix broken link to automated tests

Author: mlinksva

_articles/en-US/best-practices.md

@@ -35,7 +35,7 @@ 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.
 
-Remember to keep your documentation up-to-date. If you’re not able to always do this, delete your outdated documentation or indicate it is outdated so contributors know updates are welcome.
+Remember to keep your documentation up-to-date. If you're not able to always do this, delete your outdated documentation or indicate it is outdated so contributors know updates are welcome.
 
 ### Write down your project's vision
 

docs/styleguide.md

@@ -6,7 +6,7 @@ From the GitHub Manual of Style, which this style guide inherits from:
 >
 > In other words, the way we write is just as important as the way we design. Consider these things when writing copy.
 
-Where possible, [automated tests](../script/test-prose) enforce style rules.
+Where possible, [automated tests](../test/prose) enforce style rules.
 
 ## Content Principles
 All written content should follow these principles: