diff --git a/README.md b/README.md
index 0fa496d..34e3509 100644
--- a/README.md
+++ b/README.md
@@ -23,15 +23,11 @@ The WordPress Plugin Boilerplate includes the following files:
 
 1. Copy the `plugin-name` directory into your `wp-content/plugins` directory
 2. Navigate to the *Plugins* dashboard page
-3. Locate the menu item that reads *Plugin Name*
+3. Locate the menu item that reads *TODO*
 4. Click on *Activate*
 
 This will activate the WordPress Plugin Boilerplate. Because the Boilerplate has no real functionality, nothing will be added to WordPress; however, this demonstrates exactly how your plugin should behave while you're working with it.
 
-If you uncomment Line 71, a new menu item will be added to the *Plugins* menu in the class file which contains the following line:
-
-`add_action( 'admin_menu', array( $this, 'add_plugin_admin_menu' ) );`
-
 ## Recommended Tools
 
 ### Localization Tools
@@ -115,4 +111,4 @@ For more, in-depth information about this, read [this post](http://make.wordpres
 Plugin screenshots can be saved to one of two locations:
 
 1. The old way is to keep them in the root of the plugin directory. This will increase the size of the download of the plugin, but make the images accessible for those who install it. This is deprecated in the WordPress Plugin Boilerplate
-2. With the alternative way, you can save the screenshots in the `assets` directory, as well. The repository will look here for the screenshot files as well; however, they will not be included in the plugin download thus reducing the size of the plugin. As of its latest version, the WordPress Plugin Boilerplate now follows this convention.
\ No newline at end of file
+2. With the alternative way, you can save the screenshots in the `assets` directory, as well. The repository will look here for the screenshot files as well; however, they will not be included in the plugin download thus reducing the size of the plugin. As of its latest version, the WordPress Plugin Boilerplate now follows this convention.