history.doc in ruby-vpi-16.0.0

- old
+ new
@@ -3,14 +3,15 @@
 This is a record of important changes that have occurred with each release.
 
 
 h2. Version numbering system
 
-We _strictly_ follow the RubyGems project's "rational versioning policy":http://www.rubygems.org/read/chapter/7 since version 6.3.0. This @major.minor.build@ numbering policy "can be summarized":http://ablog.apress.com/?p=738 as follows:
-* an increase in the *major* number indicates that _functionally incompatible_ changes have occurred. Thus, what may have worked in the previous version may not work in the new one.
-* an increase in the *minor* number indicates that _functionally compatible_ changes have occurred. Thus, what worked in the previous version will work in the new one.
-* an increase in the *build* number indicates that the _underlying implementation_ has changed. The functionality has not changed and no features have been added. Thus, what worked in the previous version will work in the new one.
+Ruby-VPI uses the "RubyGems rational versioning policy":http://www.rubygems.org/read/chapter/7 to number its releases. This "major.minor.build" numbering policy "is summarized":http://ablog.apress.com/?p=738 as follows.
 
+* When the *major* number increases, functionally _incompatible changes_ have occurred. Thus, what may have worked in the previous version may not work in the new one.
 
-<% @history.each do |entry| %>
-<%= format_history_entry entry %>
-<% end %>
+* When the *minor* number increases, functionally _compatible changes_ have occurred. Thus, what worked in the previous version will work in the new one.
+
+* When the *build* number increases, the _underlying implementation_ has changed. The functionality has not changed and no features have been added. Thus, what worked in the previous version will work in the new one.
+
+
+<%= @history.join "\n\n" %>