From 81ec13b76def65ec5a10d5d34beea9837733a186 Mon Sep 17 00:00:00 2001
From: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>
Date: Mon, 5 Oct 2020 12:03:12 -0700
Subject: [PATCH] Update documentation-style-guide.md (#28037)

---
 contribute/style-guides/documentation-style-guide.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/contribute/style-guides/documentation-style-guide.md b/contribute/style-guides/documentation-style-guide.md
index 8aa22beafaf..167a3faee17 100644
--- a/contribute/style-guides/documentation-style-guide.md
+++ b/contribute/style-guides/documentation-style-guide.md
@@ -61,6 +61,8 @@ The following sections provide general guidelines on topics specific to Grafana
   - **Exceptions:** If an ampersand is used in the Grafana UI, then match the UI.
 - Avoid using internal slang and jargon in technical documentation.
 - Do not use two spaces after a period. Only add one space after each sentence. Do not add a space at the end of the paragraph.
+- Sentence length should be 25 words or less. If your thought is longer than 25 words, consider breaking up the sentence or changing the format to a list.
+- Paragraphs should be three sentences or fewer. Break up long paragraphs.
 
 ### File naming conventions