diff --git a/plugin-basics/index.md b/plugin-basics/index.md
index 2696a68..3d2d0e6 100644
--- a/plugin-basics/index.md
+++ b/plugin-basics/index.md
@@ -22,7 +22,7 @@ $ cd plugin-name/
 $ vim plugin-name.php
 ```
 
-In the example above, `vim` is the name of the text editor. Use whichever editor that is comfortable for you.
+In the example above, `vim` is the name of the text editor. Use whichever editor is comfortable for you.
 
 Now that you're editing your new plugin's PHP file, you'll need to add a plugin header comment. This is a specially formatted PHP block comment that contains metadata about the plugin, such as its name, author, version, license, etc. The plugin header comment must comply with the [header requirements](https://developer.wordpress.org/plugins/plugin-basics/header-requirements/), and at the very least, contain the name of the plugin.
 
@@ -74,4 +74,4 @@ When WordPress loads the list of installed plugins on the Plugins page of the Wo
 
 ## Sharing your Plugin
 
-Sometimes a plugin you create is just for your site. But many people like to share their plugins with the rest of the WordPress community. Before sharing your plugin, one thing you need to do is [choose a license](https://choosealicense.com/). This lets the user of your plugin know how they are allowed to use your code. To maintain compatibility with WordPress core, it is recommended that you pick a license that works with GNU General Public License (GPLv2+).
\ No newline at end of file
+Sometimes a plugin you create is just for your site. But many people like to share their plugins with the rest of the WordPress community. Before sharing your plugin, one thing you need to do is [choose a license](https://choosealicense.com/). This lets the user of your plugin know how they are allowed to use your code. To maintain compatibility with WordPress core, it is recommended that you pick a license that works with GNU General Public License (GPLv2+).