Fix broken links

Author: steveschmitt

doc-js/api-docs/index.html

@@ -74,7 +74,7 @@ <h2>Release Notes</h2>
 				<a href="#introduction" id="introduction" style="color: inherit; text-decoration: none;">
 					<h2>Introduction</h2>
 				</a>
-				<p>If this is your first time browsing the API, you might want to start with the <a href="/api-docs/classes/entitymanager.html">EntityManager</a> as this is the core class in Breeze.</p>
+				<p>If this is your first time browsing the API, you might want to start with the <a href="/doc-js/api-docs/classes/entitymanager.html">EntityManager</a> as this is the core class in Breeze.</p>
 				<p><a href="http://breeze.github.io/doc-samples/">Sample applications</a>, <a href="http://www.youtube.com/playlist?list=PL88C2B43249433416&feature=plcp" target="_blank">videos</a>, and <a href="http://breeze.github.io/doc-js">additional documentation</a> are also available.</p>
 				<a href="#what-is-public-and-what-is-not" id="what-is-public-and-what-is-not" style="color: inherit; text-decoration: none;">
 					<h3>What is public and what is not</h3>

doc-js/complex-properties.md

@@ -20,9 +20,9 @@ Complex types in Breeze are much like entity type's but with some key difference
 
 Every instance of a complex type object has two properties automatically added by Breeze:
 
-- A <a href="/doc-js/api-docs/classes/ComplexType.html" target="_blank">complexType </a>property - This is the type metadata for the specific complex type that describes this object. A `complexType` property is analogous to the `entityType` property on Breeze entities.
+- A <a href="/doc-js/api-docs/classes/complextype.html" target="_blank">complexType </a>property - This is the type metadata for the specific complex type that describes this object. A `complexType` property is analogous to the `entityType` property on Breeze entities.
 
-- A <a href="/doc-js/api-docs/classes/ComplexAspect.html" target="_blank">complexAspect </a>property - This contains information about the 'parentage' of this instance and any original values for change tracking purposes. The `complexAspect` is analogous to the `entityAspect` property on every Breeze entities.
+- A <a href="/doc-js/api-docs/classes/complexaspect.html" target="_blank">complexAspect </a>property - This contains information about the 'parentage' of this instance and any original values for change tracking purposes. The `complexAspect` is analogous to the `entityAspect` property on every Breeze entities.
 
 ## Interactions involving Complex types
 

doc-js/date-and-time.md

@@ -17,7 +17,7 @@ Remember, though, that Breeze on the client serializes per ISO 8601 and there is
 
 ## New entity *DateTime* values
 
-The metadata determine how Breeze initializes the *DateTime* property of a newly-created entity. The property will be *null* if the property is nullable. If the property is not nullable (i.e., required), Breeze sets it to the constant value in <a href="/doc-js/api-docs/classes/DataType.html#property_DateTime" target="_blank">`breeze.DataType.DateTime.defaultValue`</a>. That default is "January 1, 1900". You can change this value for your application as long as you do so *before* fetching or setting metadata.
+The metadata determine how Breeze initializes the *DateTime* property of a newly-created entity. The property will be *null* if the property is nullable. If the property is not nullable (i.e., required), Breeze sets it to the constant value in <a href="/doc-js/api-docs/classes/datatype.html#datetime" target="_blank">`breeze.DataType.DateTime.defaultValue`</a>. That default is "January 1, 1900". You can change this value for your application as long as you do so *before* fetching or setting metadata.
 
 #### Custom initialization
 

doc-js/download.html

@@ -26,9 +26,9 @@ <h1>Download</h1>
         <img src="https://cldup.com/Rg6WLgqccB.svg" title="BreezeJS on npm" width="78px" />
       </div>
       <h2 style="text-align:center">Breeze on npm</h2>
-      <p>Two npm packages: <a href="https://www.npmjs.com/packages/breeze-client"
+      <p>Two npm packages: <a href="https://www.npmjs.com/package/breeze-client"
           target="_blank"><em>breeze-client</em></a> (core) and <a
-          href="https://www.npmjs.com/packages/breeze-client-labs" target="_blank"><em>breeze-client-labs</em></a>
+          href="https://www.npmjs.com/package/breeze-client-labs" target="_blank"><em>breeze-client-labs</em></a>
         (labs).</p>
       <p>In a terminal or console window, positioned on your client directory, type:<br />
         <code>npm install breeze-client</code><br /> <code>npm install breeze-client-labs</code></p>

doc-js/entity-serialization.md

@@ -36,7 +36,7 @@ Your custom ***unmapped*** properties present a greater challenge. Breeze serial
 
 You can set an optional `serializerFn` property of the `MetadataStore` and `EntityType` classes with your own serialization function. Breeze calls your function first when serializing entity property values. Then Breeze applies its own serialization to your function's return values, applying the techniques discussed previously. 
 
-The `serializerFn` has two parameters: the <a href="/doc-js/api-docs/classes/DataProperty.html" title="DataProperty API" target="_blank">`DataProperty`</a>  to serialize and the object's current value for that property.  If the `serializerFn` returns `undefined`, the serialization of that property is suppressed.
+The `serializerFn` has two parameters: the <a href="/doc-js/api-docs/classes/dataproperty.html" title="DataProperty API" target="_blank">`DataProperty`</a>  to serialize and the object's current value for that property.  If the `serializerFn` returns `undefined`, the serialization of that property is suppressed.
 
 Use *MetadataStore.setProperties* and  *EntityType.setProperties* methods to set the `serializerFn` property.
 

doc-js/entitymanager-and-caching.md

@@ -23,7 +23,7 @@ When you eventually ask the *EntityManager* to save, it finds the changed entiti
 
 ## Key EntityManager capabilities
 
-The following is a summary of the methods available on the EntityManager arranged by task. For a complete list of methods, please see the <a href="/doc-js/api-docs/classes/EntityManager.html">EntityManager API documentation</a>.
+The following is a summary of the methods available on the EntityManager arranged by task. For a complete list of methods, please see the <a href="/doc-js/api-docs/classes/entitymanager.html">EntityManager API documentation</a>.
 
 ## Querying for entities
 

doc-js/extending-entities.md

@@ -14,7 +14,7 @@ Breeze entities are created by calling the `EntityManager.createEntity` method o
 
     var cust = manager.createEntity('Customer');
 
-Internally that method first acquires an <a href="/doc-js/api-docs/classes/EntityType.html" target="_blank">EntityType</a> information object from a <a href="/doc-js/api-docs/classes/MetadataStore.html" target="_blank">MetadataStore</a> and then calls the type's `createEntity` method [<a href="#Note01">1</a>], e.g.,
+Internally that method first acquires an <a href="/doc-js/api-docs/classes/entitytype.html" target="_blank">EntityType</a> information object from a <a href="/doc-js/api-docs/classes/metadatastore.html" target="_blank">MetadataStore</a> and then calls the type's `createEntity` method [<a href="#Note01">1</a>], e.g.,
 
     // assume that manager's metadata was previously fetched from the server
     var store = manager.metadataStore;
@@ -64,7 +64,7 @@ It isn't *just* a mess. It feels wrong. The `isBeingEdited` property should be p
 
 # Extend the Type
 
-We'll extend the `Customer` definition by adding information to the `Customer`'s <a href="/doc-js/api-docs/classes/EntityType.html" target="_blank">*EntityType*</a> in the client-side `MetadataStore`.  We'll do this early in the application, before it makes a single call to the backend service.
+We'll extend the `Customer` definition by adding information to the `Customer`'s <a href="/doc-js/api-docs/classes/entitytype.html" target="_blank">*EntityType*</a> in the client-side `MetadataStore`.  We'll do this early in the application, before it makes a single call to the backend service.
 
 We can get a `MetadataStore` from an `EntityManager` instance [<a href="#Note02">2</a>] like so:
 

doc-js/inside-entity.md

@@ -16,13 +16,13 @@ The "Customer" is also an **entity**, a long-lived object with a permanent key.
 
 # EntityType
 
-Every Breeze entity instance has an `entityType` property that returns an [`EntityType`](/doc-js/api-docs/classes/EntityType.html) object which is the [metadata](/doc-js/metadata.html) that describe its properties and other facts about the type.
+Every Breeze entity instance has an `entityType` property that returns an [`EntityType`](/doc-js/api-docs/classes/entitytype.html) object which is the [metadata](/doc-js/metadata.html) that describe its properties and other facts about the type.
 
     var type = someCustomer.entityType;
 
 # <a name="entityaspect"></a>EntityAspect
 
-A Breeze entity is "self-tracking". It maintains its own entity state, and the means to change that state, in the ***<a href="/doc-js/api-docs/classes/EntityAspect.html" target="_blank" title="EntityAspect API">EntityAspect</a>*** object returned by its *entityAspect* property.
+A Breeze entity is "self-tracking". It maintains its own entity state, and the means to change that state, in the ***<a href="/doc-js/api-docs/classes/entityaspect.html" target="_blank" title="EntityAspect API">EntityAspect</a>*** object returned by its *entityAspect* property.
 
 An object becomes a Breeze entity when it acquires its `EntityAspect` which it does when it
 
@@ -44,7 +44,7 @@ We'll tackle the key features of `EntityAspect` in four groups.
 
 Is the entity attached to an `EntityManager` and therefore in its cache? Has it changed? If changed, is it a new entity, a modified version of an existing entity from remote storage, or an existing entity that is marked for deletion?
 
-The `entityState` property answers these questions with a value from the <a href="">[`EntityState`](/doc-js/api-docs/classes/EntityState.html) enumeration. Here are the enumeration names and their meanings:
+The `entityState` property answers these questions with a value from the <a href="">[`EntityState`](/doc-js/api-docs/classes/entitystate.html) enumeration. Here are the enumeration names and their meanings:
 
 | EntityState     | Description
 | -----------     | -----------
@@ -210,13 +210,13 @@ Breeze typically raises *propertyChanged* for each property individually. Some o
 
 Breeze properties aren't just observable. They can validate changes based on rules registered in metadata. Some of the validations are registered automatically based on information in the metadata. For example, a key property is automatically required. You can add your own custom validations as well. See the <a href="/doc-js/validation" target="_blank">Validation topic</a> for details.
 
-In brief, Breeze evaluates validation rules at prescribed times. It can also validate on demand. Call the *entityAspect.validateEntity* to validate the entire entity which means every property validation rule as well as every entity-level validation rule. You can validate a single property (all of its rules) by calling *entityAspect.<a href="/doc-js/api-docs/classes/EntityAspect.html#method_validateProperty" target="_blank">validateProperty</a>*, passing in the name of the property and an optional context. Again, see the <a href="/doc-js/validation" target="_blank">Validation topic</a> for details.
+In brief, Breeze evaluates validation rules at prescribed times. It can also validate on demand. Call the *entityAspect.validateEntity* to validate the entire entity which means every property validation rule as well as every entity-level validation rule. You can validate a single property (all of its rules) by calling *entityAspect.<a href="/doc-js/api-docs/classes/entityaspect.html#validateproperty" target="_blank">validateProperty</a>*, passing in the name of the property and an optional context. Again, see the <a href="/doc-js/validation" target="_blank">Validation topic</a> for details.
 
-A validation rule either passes or fails. If it passes, it returns null. If it fails, it returns a *<a href="/doc-js/api-docs/classes/ValidationError.html" target="_blank">ValidationError</a>* describing the problem.
+A validation rule either passes or fails. If it passes, it returns null. If it fails, it returns a *<a href="/doc-js/api-docs/classes/validationerror.html" target="_blank">ValidationError</a>* describing the problem.
 
 Every `EntityAspect` maintains a `validationErrorsCollection`. The Breeze validation engine adds a new `ValidationError` instance to that collection when a validation rules fails and removes an old `ValidationErrors` instance when its associated validation rule passes.
 
-You can't access the inner `validationErrorsCollection` directly. You can get a copy of its contents by calling *entityAspect*.*<a href="/doc-js/api-docs/classes/EntityAspect.html#method_getValidationErrors" target="_blank">getValidationErrors</a>*. You can also add to or remove *validationError*s from the `validationErrorsCollection` programmatically with the `EntityAspect` methods, *<a href="/doc-js/api-docs/classes/EntityAspect.html#method_addValidationError" target="_blank">addValidationError</a>* and *<a href="/doc-js/api-docs/classes/EntityAspect.html#method_removeValidationError" target="_blank">removeValidationError</a>*.
+You can't access the inner `validationErrorsCollection` directly. You can get a copy of its contents by calling *entityAspect*.*<a href="/doc-js/api-docs/classes/entityaspect.html#getvalidationerrors" target="_blank">getValidationErrors</a>*. You can also add to or remove *validationError*s from the `validationErrorsCollection` programmatically with the `EntityAspect` methods, *<a href="/doc-js/api-docs/classes/entityaspect.html#addvalidationError" target="_blank">addValidationError</a>* and *<a href="/doc-js/api-docs/classes/entityaspect.html#removevalidationerror" target="_blank">removeValidationError</a>*.
 
 Breeze raises the `EntityAspect.validationErrorsChanged` event when `ValidationErrors` are added or removed from the entity's `validationErrorsCollection`; you can subscribe to that event:
 
@@ -233,7 +233,7 @@ This last category is a small menagerie of miscellaneous *EntityAspect* members
 
 - ***entity***- a backward reference to the entity that holds this *EntityAspect*
 - ***entityManager*** - the *EntityManager* to which this entity is attached ... or was attached. It's null if the entity is new and not yet added to a manager.
-- ***getKey*** - a function returning the entity's [`EntityKey`](/doc-js/api-docs/classes/EntityKey.html). A key is an object that uniquely identifies the entity in cache and in remote storage. The key is not a simple JavaScript value. It's an object the identifies the type of the entity and the value ... or values ... of the key; Breeze supports entities with composite keys.
+- ***getKey*** - a function returning the entity's [`EntityKey`](/doc-js/api-docs/classes/entitykey.html). A key is an object that uniquely identifies the entity in cache and in remote storage. The key is not a simple JavaScript value. It's an object the identifies the type of the entity and the value ... or values ... of the key; Breeze supports entities with composite keys.
 - ***isBeingSaved*** - a property that returns `true` if this entity is one in a batch of entities being saved and the save operation is still in progress. Your application may need to prevent further changes to the entity until the save operation completes, successfully or not.
 - ***loadNavigationProperty*** - you can download related entities, on demand, by calling `loadNavigationProperty` as described in the [Navigation Properties](/doc-js/navigation-properties.html) topic.
 
@@ -242,7 +242,7 @@ This last category is a small menagerie of miscellaneous *EntityAspect* members
 
 You typically access the breeze entity infrastructure through the *entityAspect* property. Breeze also injects a few more entity-oriented members into the model object's prototype. These members are visible on the entity's surface API.
 
-***entityType*** - a property that returns the Breeze [type information object](/doc-js/api-docs/classes/EntityType.html) metadata describing this type of entity.
+***entityType*** - a property that returns the Breeze [type information object](/doc-js/api-docs/classes/entitytype.html) metadata describing this type of entity.
 
     var customerType = manager.metadataStore.getEntityType("Customer");
     var customer = customerType.createEntity();

doc-js/lap-add-entity.md

@@ -54,7 +54,7 @@ But there are important Breeze lessons to learn from this long-form of entity cr
 
 Every entity instance has a type that you can access through its `entityType` property. The type of an entity is itself an object, an instance of the Breeze `EntityType`.
 
-The `EntityType` is a container for metadata that describe a Breeze entity type. It knows about the type's constructor, validation rules, and properties; the detail about properties is wide ranging (check out the <a href="/doc-js/api-docs/classes/DataProperty.html">`DataProperty`</a> metadata object in the Breeze API docs). 
+The `EntityType` is a container for metadata that describe a Breeze entity type. It knows about the type's constructor, validation rules, and properties; the detail about properties is wide ranging (check out the <a href="/doc-js/api-docs/classes/dataproperty.html">`DataProperty`</a> metadata object in the Breeze API docs). 
 
 Perhaps most importantly, the `EntityType` knows how to create new instances of an entity type. We used that feature a moment ago when we called its `createEntity` method. We got hold of an EntityType object for TodoItems from the EntityManager's *metadatastore* with this line.
 

doc-js/lap-changetracking.md

@@ -48,7 +48,7 @@ You delete an entity by changing its `EntityState` to "Deleted" like this:
 `setDeleted` does not destroy the object locally nor does it remove the entity from the database. The entity simply remains in cache in its new "Deleted" state ... as changed and added entities do. A successful save does delete the entity from the database and remove it from cache.
 
 ## PropertyChanged
-A Breeze entity property raises a `propertyChanged` event when it is changed to a different value. You attach an event handler to that event to listen for changes to *a* specific property of *one specific entity instance* as explained in the [API documentation for this event](/doc-js/api-docs/classes/EntityAspect.html#event_propertyChanged).
+A Breeze entity property raises a `propertyChanged` event when it is changed to a different value. You attach an event handler to that event to listen for changes to *a* specific property of *one specific entity instance* as explained in the [API documentation for this event](/doc-js/api-docs/classes/entityaspect.html#propertychanged).
 
     // assume order is an order entity attached to an EntityManager.
     order.entityAspect.propertyChanged.subscribe(function (propertyChangedArgs) {
@@ -114,9 +114,9 @@ You just learned how to listen for a change to *a single Knockout property of a
 
 ## EntityManager.entityChanged Event
 
-The `EntityManager` is always watching for changes to entities in its cache and when it detects a change to an entity, it raises the [entityChanged event](/doc-js/api-docs/classes/EntityManager.html#event_entityChanged). 
+The `EntityManager` is always watching for changes to entities in its cache and when it detects a change to an entity, it raises the [entityChanged event](/doc-js/api-docs/classes/entitymanager.html#entitychanged). 
 
-The manager raises the event when it detects many different kinds of changes which it calls "entity actions". The Breeze [`EntityAction` enumeration](/doc-js/api-docs/classes/EntityAction.html) describes them.
+The manager raises the event when it detects many different kinds of changes which it calls "entity actions". The Breeze [`EntityAction` enumeration](/doc-js/api-docs/classes/entityaction.html) describes them.
 
 Here's how you might subscribe to `eventChanged` to respond to property changes: