Skip to content

Commit

Permalink
Improve readability
Browse files Browse the repository at this point in the history
  • Loading branch information
mjackson committed Oct 5, 2015
1 parent ed379c9 commit 3fd8224
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,16 +1,16 @@
# history

[![build status](https://img.shields.io/travis/rackt/history/master.svg?style=flat-square)](https://travis-ci.org/rackt/history)
[![npm package](https://img.shields.io/npm/v/history.svg?style=flat-square)](https://www.npmjs.org/package/history)
[![react-router channel on slack](https://img.shields.io/badge/[email protected]?style=flat-square)](http://www.reactiflux.com)

## history

[`history`](https://www.npmjs.com/package/history) is a JavaScript library that lets you easily manage session history in browsers, testing environments, and (soon, via [React Native](https://facebook.github.io/react-native/)) native devices. `history` abstracts away the differences in these different platforms and provides a minimal API that lets you manage the history stack, navigate, confirm navigation, and persist state between sessions. `history` is library-agnostic and may easily be included in any JavaScript project.

### Installation
## Installation

$ npm install history

### Basic Usage
## Basic Usage

A "history" encapsulates navigation between different screens in your app, and notifies listeners when the current screen changes.

Expand All @@ -33,7 +33,7 @@ unlisten()

You can find many more examples [in the documentation](https://github.com/rackt/history/tree/master/docs)!

### Thanks
## Thanks

A big thank-you to [Dan Shaw](https://www.npmjs.com/~dshaw) for letting us use the `history` npm package name! Thanks Dan!

Expand Down

0 comments on commit 3fd8224

Please sign in to comment.