diff --git a/guide/english/accessibility/accessibility-basics/index.md b/guide/english/accessibility/accessibility-basics/index.md
index 61cb0c9343..c231f59235 100644
--- a/guide/english/accessibility/accessibility-basics/index.md
+++ b/guide/english/accessibility/accessibility-basics/index.md
@@ -15,7 +15,6 @@ As an increasing number of new technologies are being created, the toolbox of a
 One tool in that toolbox should be accessibility. It should be one of the very first steps of creating any form of web content, yet is not considered enough. This could be due to a simple case of not knowing it even exists or an extreme case like not caring about it at all.
 
 If you are reading this article, you may be 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 feel that there is a legal obligation from your employer, and you need to learn more about it.
@@ -28,7 +27,7 @@ The word "accessibility" in itself can be a bit misleading at times, especially
 
 In one sense, if your site is public on the Internet, that website is accessible to everyone with a web browser.
 
-But is all the content on your website actually readable, usable, and understandable for everyone? Are there no thresholds that bar certain  people from "accessing" all the information you are exposing?
+But, is all the content on your website actually readable, usable, and understandable by everyone? Are there no thresholds that bar certain people from 'accessing' all the information you are exposing?
 
 You could ask yourself questions such as the following: