docs: Adds Meteor and Mongoose links.

Author: ryasmi

docs/options.md

@@ -12,7 +12,7 @@ The [facade](./facade.md) [functions](./functions.md) have some common options t
 ### Id
 This is a string that uniquely identifies an entity. In some databases the identifier for an entity may actually be stored as a different data type (e.g. a number or MongoId), but the Facade functions will always convert this to a string for compatibility across database implementations.
 
-It's important to know that these identifiers are user-defined, meaning that they will not be generated by the database. The reason for this is that allowing the user to define the identifier enables optimistic updates to be handled more easily especially on the client-side. Frameworks and libraries like Meteor also work in this way.
+It's important to know that these identifiers are user-defined, meaning that they will not be generated by the database. The reason for this is that allowing the user to define the identifier enables optimistic updates to be handled more easily, especially on the client-side. Frameworks and libraries like [Meteor](https://www.meteor.com/) and [Mongoose](http://mongoosejs.com/) also work in this way.
 
 Having said all of that, there may be ways to allow the database to generate the identifiers in concrete implementations of the Facade, but only when you can specify `constructDocument` and `constructEntity` properties in the factory of those implementations. [The Knex implementation of the Facade](https://github.com/js-entity-repos/knex/blob/master/readme.md) is an example of a concrete implementation that allows you to specify these properties in its factory.