From 8effa95a96828a5e0972215d68da7de18809dd0f Mon Sep 17 00:00:00 2001
From: Ana Martins <60753223+OutSystemsAMM@users.noreply.github.com>
Date: Tue, 7 Nov 2023 22:37:26 +0000
Subject: [PATCH] Fixed what looks like a markdown formatting issue. (#826)

---
 articles/what_makes_documentation_good.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/articles/what_makes_documentation_good.md b/articles/what_makes_documentation_good.md
index 22892fd0..7c3d6c40 100644
--- a/articles/what_makes_documentation_good.md
+++ b/articles/what_makes_documentation_good.md
@@ -36,7 +36,7 @@ Badly written text is taxing to read. Minimize the tax on readers by writing wel
 
 **Avoid demonstrative pronouns (e.g., “this”), especially across sentences.** For example, instead of saying “Building on our discussion of the previous topic, now let’s discuss function calling” try “Building on message formatting, now let’s discuss function calling.” The second sentence is easier to understand because it doesn’t burden the reader with recalling the previous topic. Look for opportunities to cut demonstrative pronouns altogether: e.g., “Now let’s discuss function calling.”
 
-**\*Be consistent.** Human brains are amazing pattern matchers.\* Inconsistencies will annoy or distract readers. If we use Title Case everywhere, use Title Case. If we use terminal commas everywhere, use terminal commas. If all of the Cookbook notebooks are named with underscores and sentence case, use underscores and sentence case. Don’t do anything that will cause a reader to go ‘huh, that’s weird.’ Help them focus on the content, not its inconsistencies.
+**Be consistent.** Human brains are amazing pattern matchers. Inconsistencies will annoy or distract readers. If we use Title Case everywhere, use Title Case. If we use terminal commas everywhere, use terminal commas. If all of the Cookbook notebooks are named with underscores and sentence case, use underscores and sentence case. Don’t do anything that will cause a reader to go ‘huh, that’s weird.’ Help them focus on the content, not its inconsistencies.
 
 **Don’t tell readers what they think or what to do.** Avoid sentences like “Now you probably want to understand how to call a function” or “Next, you’ll need to learn to call a function.” Both examples presume a reader’s state of mind, which may annoy them or burn our credibility. Use phrases that avoid presuming the reader’s state. E.g., “To call a function, …”