More HISTORY.md updates. OCD changes.

src/anim/HISTORY.md

@@ -9,7 +9,7 @@ Anim Change History
 3.7.2
 -----
 
-* No changes
+* No changes.
 
 3.7.1
 -----

src/arraysort/HISTORY.md

@@ -9,7 +9,7 @@ ArraySort Change History
 3.7.2
 -----
 
-* No changes
+* No changes.
 
 3.7.1
 -----

src/async-queue/HISTORY.md

@@ -9,7 +9,7 @@ AsyncQueue Change History
 3.7.2
 -----
 
-* No changes
+* No changes.
 
 3.7.1
 -----
@@ -70,10 +70,10 @@ AsyncQueue Change History
 -----
 
   * [!] `queue-base` is now part of `yui`.
-  
+
   * [!] `queue-run` was renamed `async-queue` and both `async-queue` and
     `queue-promote` are now independent modules.
-    
+
   * `AsyncQueue` defaults to asynchronous callback execution (again).
 
 3.0.0beta1

src/attribute/HISTORY.md

@@ -9,7 +9,7 @@ Attribute Change History
 3.7.2
 -----
 
-* No changes
+* No changes.
 
 3.7.1
 -----

src/autocomplete/HISTORY.md

@@ -9,7 +9,7 @@ AutoComplete Change History
 3.7.2
 -----
 
-* No changes
+* No changes.
 
 3.7.1
 -----

src/base/HISTORY.md

@@ -9,7 +9,7 @@ Base Change History
 3.7.2
 -----
 
-* No changes
+* No changes.
 
 3.7.1
 -----
@@ -24,14 +24,14 @@ Base Change History
 3.6.0
 -----
 
-  * "value" defined in a subclass ATTRS definition, will now override 
-    "valueFn" for the same attribute from the superclass chain. 
-    
-    Previously, "value" would only override "value" and "valueFn" 
-    would only overide "valueFn", and in the aggregated set of 
-    attributes, "valueFn" would take precedence over "value". 
-    
-    This meant that subclasses had to define a "valueFn" to overide 
+  * "value" defined in a subclass ATTRS definition, will now override
+    "valueFn" for the same attribute from the superclass chain.
+
+    Previously, "value" would only override "value" and "valueFn"
+    would only overide "valueFn", and in the aggregated set of
+    attributes, "valueFn" would take precedence over "value".
+
+    This meant that subclasses had to define a "valueFn" to overide
     superclasses, if the superclass used "valueFn".
 
 3.5.1
@@ -42,12 +42,12 @@ Base Change History
 3.5.0
 -----
 
-  * Only invoke Base constructor logic once to 
+  * Only invoke Base constructor logic once to
     support multi-inheritance scenario in which
     an extension passed to Base.create inherits from Base
     itself.
 
-    NOTE: To support multiple inhertiance more deeply, we'd 
+    NOTE: To support multiple inhertiance more deeply, we'd
     need to remove the hasOwnProperty restriction around object
     key iteration.
 
@@ -56,8 +56,8 @@ Base Change History
 
     Y.BaseCore still maintains the ATTRS handling, init/destroy
     lifecycle and plugin support, but doesn't fire any custom evnets
-    of it's own (the idea is that it will the base for Node-Plugin 
-    type components, built off of a WidgetCore) 
+    of it's own (the idea is that it will the base for Node-Plugin
+    type components, built off of a WidgetCore)
 
     Y.Base is now Y.BaseCore + Y.Attribute, and is 100% backwards
     compatible.
@@ -66,7 +66,7 @@ Base Change History
 
     Y.Attribute     - Common Attribute Functionality (100% backwards compat)
     Y.Base          - Common Base Functionality (100% backwards compat)
-   
+
     Y.AttributeCore - Lightest Attribute support, without CustomEvents
     Y.BaseCore      - Lightest Base support, without CustomEvents
 
@@ -77,21 +77,21 @@ Base Change History
     Y.AttributeComplex - Augmentable support for constructor complex attribute parsing ({"x.y":foo})
 
     --
- 
+
     Y.Attribute = Y.AttributeCore + Y.AttributeEvents + Y.AttributeExtras
     Y.Base      = Y.BaseCore + Y.Attribute
 
-    -- 
+    --
 
     Modules:
-    
+
     "base-base" : Y.Base
     "base-core" : Y.BaseCore
 
     "base-build" : Y.Base.build/create/mix mixin
 
   * Extended Base.create/mix support for _buildCfg, to Extensions, mainly so that
-    extensions can define a whitelist of statics which need to be copied to the 
+    extensions can define a whitelist of statics which need to be copied to the
     main class.
 
     e.g.
@@ -114,7 +114,7 @@ Base Change History
 
   * Base now destroys plugins before destroying itself
 
-  * Base.create/mix extensions can now define initializer and 
+  * Base.create/mix extensions can now define initializer and
     destructor prototype functions, which will get invoked after
     the initializer for the host class into which they are mixed and
     before it's destructor.
@@ -138,14 +138,14 @@ Base Change History
   * Fixed Base.create to properly isolate ATTRS on extensions
 
 3.1.1
------	
+-----
 
-  * No changes 
+  * No changes
 
 3.1.0
 -----
 
-  * As the final step in the destroy phase, Base now does a detachAll() to avoid invoking listeners 
+  * As the final step in the destroy phase, Base now does a detachAll() to avoid invoking listeners
     which may be waiting to be in an async. step which occurs after destruction.
 
   * "init" and "destroy" events are now published with the defaultTargetOnly property set to true
@@ -154,41 +154,41 @@ Base Change History
     to define their own event prefix
 
   * Made "init" and "destroy" events fireOnce:true (along with
-    "render" in Widget), so that subscriptions made after the 
+    "render" in Widget), so that subscriptions made after the
     events are fired, are notified immediately.
 
-  * Dynamic and non-dynamically built classes now have their 
+  * Dynamic and non-dynamically built classes now have their
     extensions instantiated the same way - during _initHierarchy.
 
-  * Updated ATTRS handling for Base.build, so that ATTRS are 
-    also aggregated at the attribute configuration object level, 
-    allowing extensions to add to, or overwrite, attribute 
+  * Updated ATTRS handling for Base.build, so that ATTRS are
+    also aggregated at the attribute configuration object level,
+    allowing extensions to add to, or overwrite, attribute
     configuration properties on the host.
 
-  * Added sugar Base.create and Base.mix methods on top of 
-    Base.build, to simplify the 2 main use cases: 
+  * Added sugar Base.create and Base.mix methods on top of
+    Base.build, to simplify the 2 main use cases:
 
     1) Creating a completely new class which uses extensions.
     2) Mixing in extensions to an existing class.
 
-  * Documented non-attribute on, after, bubbleTargets and plugins 
-    property support in the Base constructor config argument 
+  * Documented non-attribute on, after, bubbleTargets and plugins
+    property support in the Base constructor config argument
 
 3.0.0
 -----
 
   * Fixed hasImpl method on built classes, to look up the class
     hierarchy for applied extensions.
 
-  * Plugin.Host removed from base-base module and delivered as it's 
+  * Plugin.Host removed from base-base module and delivered as it's
     own module - "pluginhost"
 
   * base broken up into..
 
-     base-base: Provides class hierarchy support for ATTRS and 
+     base-base: Provides class hierarchy support for ATTRS and
      initialization
 
-     base-build: Provides Extension support in the form of 
+     base-build: Provides Extension support in the form of
      Base.build
 
      base-pluginhost: Augments Plugin.Host to Base, adding plugin
@@ -197,33 +197,33 @@ Base Change History
 3.0.0 beta 1
 ------------
 
-  * Config argument for init event now merged into the event facade, 
+  * Config argument for init event now merged into the event facade,
     instead of being passed separately (available as e.cfg).
-  
+
   * Removed Base.create. On review, considered to be overkill.
     Users can easily create new instances, using Base.build
 
-  * Moved PluginHost down from Widget to Base, since utils and 
+  * Moved PluginHost down from Widget to Base, since utils and
     Node will also support Plugins.
 
-  * PluginHost.plug and unplug now accept the plugin class as 
+  * PluginHost.plug and unplug now accept the plugin class as
     arguments [plug(pluginClass, cfg) and unplug(pluginClass)].
 
   * Split base module up into base-base and base-build.
 
   * Added lazy attribute initialization support, to improve performance.
-  
-    This also removes order dependency when processing ATTRS for a 
+
+    This also removes order dependency when processing ATTRS for a
     particular class.
 
-    If a get/set call is made for an uninitialized attribute A, in the 
-    getter/setter/validator or valueFns of another attribute B, A will 
-    be intiailized on the fly. 
+    If a get/set call is made for an uninitialized attribute A, in the
+    getter/setter/validator or valueFns of another attribute B, A will
+    be intiailized on the fly.
 
-  * Added ability to subscribe to on/after events through the 
+  * Added ability to subscribe to on/after events through the
     constructor config object, e.g.:
 
-      new MyBaseObject({ 
+      new MyBaseObject({
          on: {
             init: handlerFn,
             myAttrChange: handlerFn
@@ -247,12 +247,12 @@ Base Change History
 
     If the cloneDefaultValue property is not defined, Base will clone
     any Arrays or Object literals which are used as default values when
-    configuring attributes for an instance, so that updates to instance 
+    configuring attributes for an instance, so that updates to instance
     values do not modify the default value.
 
     This behavior can be over-ridden using the cloneDefaultValue property:
 
-    true, deep: 
+    true, deep:
 
       Use Y.clone to protect the default value.
 
@@ -267,14 +267,14 @@ Base Change History
       a utility object.
 
   * Base.plug and Base.unplug used to add static Plugins (default plugins
-    for a class). Replaces static PLUGINS array, allowing subclasses to 
+    for a class). Replaces static PLUGINS array, allowing subclasses to
     easily unplug static plugins added higher up in the hierarchy.
 
   * Base adds all attributes lazily. This means attributes don't get
     initialized until the first call to get/set, speeding up construction
     of Base based objects.
 
-    Attributes which have setters which set some other state in the object, 
+    Attributes which have setters which set some other state in the object,
     can configure the attribute to disable lazy initialization, by setting
     lazyAdd:false as part of their attribute configuration, so that the setter
     gets invoked during construction.

src/button/HISTORY.md

@@ -9,7 +9,7 @@ Button Change History
 3.7.2
 -----
 
-* No changes
+* No changes.
 
 3.7.1
 -----

src/calendar/HISTORY.md

@@ -9,7 +9,7 @@ Calendar Change History
 3.7.2
 -----
 
-* No changes
+* No changes.
 
 3.7.1
 -----

src/classnamemanager/HISTORY.md

@@ -9,7 +9,7 @@ ClassName Manager Change History
 3.7.2
 -----
 
-* No changes
+* No changes.
 
 3.7.1
 -----

src/console-filters/HISTORY.md

@@ -9,7 +9,7 @@ ConsoleFilters Plugin Change History
 3.7.2
 -----
 
-* No changes
+* No changes.
 
 3.7.1
 -----
@@ -48,7 +48,7 @@ ConsoleFilters Plugin Change History
 
 3.3.0
 -----
-    
+
   * No changes.
 
 3.2.0
@@ -74,5 +74,5 @@ ConsoleFilters Plugin Change History
 
 3.0.0beta1
 -----------
-    
+
   * Initial release.

src/console/HISTORY.md

@@ -11,7 +11,7 @@ Console Change History
 3.7.2
 -----
 
-* No changes
+* No changes.
 
 3.7.1
 -----

src/cookie/HISTORY.md

@@ -9,7 +9,7 @@ Cookie Change History
 3.7.2
 -----
 
-* No changes
+* No changes.
 
 3.7.1
 -----
@@ -83,7 +83,7 @@ Cookie Change History
 
   * Synchronized with the 2.x version of cookie:
     * Changes formatting of date from `toGMTString()` to `toUTCString()` (trac#
-      2527892). 
+      2527892).
     * Updated `remove()` so that it no longer modifies the options object that
       is passed in (trac# 2527838).
     * Changed behavior for Boolean cookies (those that don't contain an equals
@@ -100,7 +100,7 @@ Cookie Change History
       `set()` and `get()`. (trac# 2527953).
     * Changed `get()` to take an options object with `raw` and `converter`
       properties. If a function is passed instead of an object then it is used
-      as the converter for backward compatibility (trac# 2527953).  
+      as the converter for backward compatibility (trac# 2527953).
 
 
 3.0.0pr2