README.rdoc in bones-2.2.0 vs README.rdoc in bones-2.3.0

@@ -8,37 +8,10 @@
 The skeleton contains some starter code and a collection of rake tasks to
 ease the management and deployment of your source code. Mr Bones is not
 viral -- all the code your project needs is included in the skeleton (no
 gem dependency required).
 
-== VERSION 2.1.0 CHANGES:
-
-With my Mr Bones projects, I found myself constantly updating the tasks as new
-versions of Mr Bones were released. This quickly became annoying. Why not use
-the tasks from the Mr Bones gem and only copy those tasks to my own projects
-when they are packaged and released? That is the goal of this release of Mr
-Bones.
-
-Version 2.1.0 of Mr Bones allows your projects to use the rake tasks found
-in the Mr Bones gem but still remain independent from Mr Bones when
-deployed. This is accomplished by copying the rake tasks into your project
-only when it is packaged into a gem (or zip file or tarball).
-
-You still have the option of copy the tasks to your local project when it is
-created. Or you can add tasks to your project at a later time.
-
-So, if you have an exsiting project and you want to use the Mr Bones tasks,
-simply delete your "tasks" folder and put the following at the top of your
-Rakefile:
-
-  begin
-    require 'bones'
-    Bones.setup
-  rescue LoadError
-    load 'tasks/setup.rb'   # this line should already be there
-  end
-
 == FEATURES:
 
 Mr Bones provides the following rake tasks:
 
   ann               # Alias to ann:announcement
@@ -62,22 +35,21 @@
   gem:repackage     # Force a rebuild of the package files
   gem:spec          # Write the gemspec
   gem:uninstall     # Uninstall the gem
   git:create_tag    # Create a new tag in the Git repository
   git:show_tags     # Show tags from the Git repository
-  manifest          # Alias to manifest:check
-  manifest:check    # Verify the manifest
-  manifest:create   # Create a new manifest
   notes             # Enumerate all annotations
   notes:fixme       # Enumerate all FIXME annotations
   notes:optimize    # Enumerate all OPTIMIZE annotations
   notes:todo        # Enumerate all TODO annotations
   spec              # Alias to spec:run
   spec:rcov         # Run all specs with RCov
   spec:run          # Run all specs with basic output
   spec:specdoc      # Run all specs with text output
   spec:verify       # Verify that rcov coverage is at least 90.0%
+  svn:create_tag    # Create a new tag in the SVN repository
+  svn:show_tags     # Show tags from the SVN repository
   test              # Alias to test:run
   test:rcov         # Run rcov on the unit tests
   test:run          # Run tests for run
 
 The rake tasks in the Mr Bones framework can be found in the "tasks"
@@ -366,5 +338,33 @@
   ann_text              => ann.text
   ann_paragraphs        => ann.paragraphs
   ann_email             => ann.email     
 
 And of course, each name should be prepended with PROJ in your Rakefile.
+
+== VERSION 2.1.0 CHANGES:
+
+With my Mr Bones projects, I found myself constantly updating the tasks as new
+versions of Mr Bones were released. This quickly became annoying. Why not use
+the tasks from the Mr Bones gem and only copy those tasks to my own projects
+when they are packaged and released? That is the goal of this release of Mr
+Bones.
+
+Version 2.1.0 of Mr Bones allows your projects to use the rake tasks found
+in the Mr Bones gem but still remain independent from Mr Bones when
+deployed. This is accomplished by copying the rake tasks into your project
+only when it is packaged into a gem (or zip file or tarball).
+
+You still have the option of copy the tasks to your local project when it is
+created. Or you can add tasks to your project at a later time.
+
+So, if you have an exsiting project and you want to use the Mr Bones tasks,
+simply delete your "tasks" folder and put the following at the top of your
+Rakefile:
+
+  begin
+    require 'bones'
+    Bones.setup
+  rescue LoadError
+    load 'tasks/setup.rb'   # this line should already be there
+  end
+