diff --git a/README.txt b/README.txt
index a98e614..dbeb9eb 100644
--- a/README.txt
+++ b/README.txt
@@ -7,14 +7,13 @@ are reset, and the (localized) words "Clone of" are inserted into the title to
 remind you that you are not editing the original node.
 
 Users with the "clone node" or "clone own nodes" permission can utilize this
-functionality. A new tab will appear on node pages with the word "Clone".
+functionality. A "Clone content" local action link will appear on node pages.
 Depending on the setting you choose there are two possible actions that will
 occur when you click that tab. Each of these is a different cloning "method".
 
-The default method (used in the 5.x-2.x branch also) works by pre-populating the
-node form, rather than immediately saving a copy of the original node to the
-database.  Thus, your node will not be saved until you hit "Submit" (just like
-if you went to node/add/x).
+The default method works by pre-populating the node form, rather than immediately
+saving a copy of the original node to the database.  Thus, your node will not
+be saved until you hit "Submit" (just like if you went to node/add/x).
 
 The alternative method that may be selected immediately saves the node (by
 default the user must confirm this action on a confirmation form). This may
@@ -25,21 +24,21 @@ This module makes reasonable checks on access permissions.  A user cannot clone
 a node unless they can use the input format of that node, and unless they have
 permission to create new nodes of that type based on a call to node_access().
 
-Settings can be accessed at admin/settings/clone.  On this page you can
+Settings can be accessed at admin/config/content/clone.  On this page you can
 set whether the publishing options are reset when making a clone of a node.
 This is set for each node type individually.
 
 This module seems to work with common node types, however YMMV, especially with
-nodes that have any sort of image or file  attachments.   In all cases, but
-especially if you are using a complex (CCK) or custom node type, you should
-evaluate this module on a test site with a copy of your database before
-attempting to use it on a live site. On the settings page you may choose
+nodes that have any sort of image or file  attachments.  In all cases, but
+especially if you are using a complex (non-core) field or custom node type,
+you should evaluate this module on a test site with a copy of your database
+before attempting to use it on a live site. On the settings page you may choose
 node types to be omitted from the cloning mechanism - no users will be able
 to clone a node of an omitted type.
 
 This module makes no attempt to respect field-level permissions set via
-CCK's Content Permissions module, or any other module that implements
-CCK field-level permissions hooks. You should test your configuration
+the Field Permissions module, or any other module that implements
+field-level permissions hooks. You should test your configuration
 carefully or not allow access to the clone functionality for non-admins if
 you rely on field-level permissions for important site features.