good catch, fixed it! mind taking a second look, so i can rebase it & merge?
On Sat, Feb 28, 2015 at 11:21 PM, kxepal <[email protected]> wrote: > Github user kxepal commented on a diff in the pull request: > > https://github.com/apache/couchdb-fabric/pull/18#discussion_r25561896 > > --- Diff: README.md --- > @@ -1,24 +1,18 @@ > ## fabric > > -Fabric is a collection of proxy functions for [CouchDB][1] operations in > a cluster. These functions are used in [BigCouch][2] as the remote procedure > endpoints on each of the cluster nodes. > +Fabric is a collection of proxy functions for [CouchDB][1] operations in > a cluster. These functions are used in CouchDB as the remote procedure > endpoints on each of the cluster nodes. > > -For example, creating a database is a straightforward task in standalone > CouchDB, but for BigCouch, each node that will store a shard for the database > needs to receive and execute a fabric function. The node handling the > request also needs to compile the results from each of the nodes and respond > accordingly to the client. > +For example, creating a database is a straightforward task in CouchDB > 1.x, but for a clustered CouchDB, each node that will store a shard for the > database needs to receive and execute a fabric function. The node handling > the request also needs to compile the results from each of the nodes and > respond accordingly to the client. > > -Fabric is used in conjunction with 'Rexi' which is also an application > within BigCouch. > +Fabric is used in conjunction with 'Rexi' which is also an application > within CouchDB. > > ### Getting Started > -Fabric requires R13B03 or higher and can be built with [rebar][6], which > comes bundled in the repository. > +Fabric requires R13B03 or higher and can be built with [rebar][3], which > comes bundled in the repository. > --- End diff -- > > oh..well, it's not bundled anymore. > > > --- > If your project is set up for it, you can reply to this email and have your > reply appear on GitHub as well. If your project does not have this feature > enabled and wishes so, or if the feature is enabled but not working, please > contact infrastructure at [email protected] or file a JIRA ticket > with INFRA. > ---
