From 7e35a86038b8cdf0debd3f4c1f1e6bda6f814030 Mon Sep 17 00:00:00 2001 From: Hafid Feghouli Date: Sun, 14 Oct 2018 12:27:30 -0400 Subject: [PATCH] fix(documentation): dots added. (#18526) Added dots at end of 2 sentences. --- .../guide/english/accessibility/accessibility-basics/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/client/src/pages/guide/english/accessibility/accessibility-basics/index.md b/client/src/pages/guide/english/accessibility/accessibility-basics/index.md index 5cb6bf4123..1613235a11 100644 --- a/client/src/pages/guide/english/accessibility/accessibility-basics/index.md +++ b/client/src/pages/guide/english/accessibility/accessibility-basics/index.md @@ -14,8 +14,8 @@ One tool in that toolbox should be accessibility. It is a tool that should ideal In my life as a user, and later a developer, who benefits from accessibility in any form of content, I have seen both ends of that spectrum. If you are reading this article, I am guessing you are in one of the following categories: -* You are a novice web developer and would like to know more about accessibility -* You are a seasoned web developer and have lost your way (more on that later) +* You are a novice web developer and would like to know more about accessibility. +* You are a seasoned web developer and have lost your way (more on that later). * You feel that there is a legal obligation from work, and need to learn more about it. If you fall outside these rather broad categories, please let me know. I always like to hear from the people who read what I write about. Implementing accessibility impacts the entire team, from the colors chosen by the designer, the copy written by the copywriter, and to you, the developer.