Rename Terms.md => Glossary.md

remix-run · Oct 13, 2015 · f5292c2 · f5292c2
1 parent 0275b5a
commit f5292c2
Show file tree

Hide file tree

Showing 7 changed files with 8 additions and 8 deletions.
diff --git a/docs/BasenameSupport.md b/docs/BasenameSupport.md
@@ -1,6 +1,6 @@
 ## Basename Support
 
-Support for running an app under a "base" URL is provided by the `useBasename` [enhancer](Terms.md#createhistoryenhancer) function. Simply use a wrapped version of your `createHistory` function to create your `history` object and you'll have the correct `location.pathname` inside `listen` and `listenBefore` hooks.
+Support for running an app under a "base" URL is provided by the `useBasename` [enhancer](Glossary.md#createhistoryenhancer) function. Simply use a wrapped version of your `createHistory` function to create your `history` object and you'll have the correct `location.pathname` inside `listen` and `listenBefore` hooks.
 
 ```js
 import { createHistory, useBasename } from 'history'

diff --git a/docs/ConfirmingNavigation.md b/docs/ConfirmingNavigation.md
@@ -1,6 +1,6 @@
 ## Confirming Navigation
 
-Sometimes you may want to prevent the user from going to a different page. For example, if they are halfway finished filling out a long form, and they click the back button, you may want to prompt them to confirm they actually want to leave the page before they lose the information they've already entered. For these cases, `history` lets you register [transition hooks](Terms.md#transitionhook) that return a prompt message you can show the user before the [location](Terms.md#location) changes. For example, you could do something like this:
+Sometimes you may want to prevent the user from going to a different page. For example, if they are halfway finished filling out a long form, and they click the back button, you may want to prompt them to confirm they actually want to leave the page before they lose the information they've already entered. For these cases, `history` lets you register [transition hooks](Glossary.md#transitionhook) that return a prompt message you can show the user before the [location](Glossary.md#location) changes. For example, you could do something like this:
 
 ```js
 history.listenBefore(function (location) {
@@ -9,7 +9,7 @@ history.listenBefore(function (location) {
 })
 ```
 
-You can also simply `return false` to prevent a [transition](Terms.md#transition).
+You can also simply `return false` to prevent a [transition](Glossary.md#transition).
 
 If your transition hook needs to execute asynchronously, you can provide a second `callback` argument to your transition hook function that you must call when you're done with async work.
 

diff --git a/docs/GettingStarted.md b/docs/GettingStarted.md
@@ -1,6 +1,6 @@
 ## Getting Started
 
-The first thing you'll need to do is create a [history object](Terms.md#history). The main `history` module exports several different [`create*` methods](Terms.md#createhistory) that you can use depending on your environment.
+The first thing you'll need to do is create a [history object](Glossary.md#history). The main `history` module exports several different [`create*` methods](Glossary.md#createhistory) that you can use depending on your environment.
 
 - `createHistory` is for use in modern web browsers that support the [HTML5 history API](http://diveintohtml5.info/history.html) (see [cross-browser compatibility](http://caniuse.com/#feat=history))
 - `createHashHistory` is for use in legacy web browsers (see [caveats of using hash history](HashHistoryCaveats.md))
@@ -33,7 +33,7 @@ You can also use a `history` object to programmatically change the current `loca
 - `goBack()`
 - `goForward()`
 
-The [`path`](Terms.md#path) argument to `pushState` and `replaceState` represents a complete URL path, including the [query string](Terms.md#querystring). The [`state`](Terms.md#locationstate) argument should be a JSON-serializable object.
+The [`path`](Glossary.md#path) argument to `pushState` and `replaceState` represents a complete URL path, including the [query string](Glossary.md#querystring). The [`state`](Glossary.md#locationstate) argument should be a JSON-serializable object.
 
 ```js
 // Push a new entry onto the history stack.

diff --git a/docs/Terms.md → docs/Glossary.md b/docs/Terms.md → docs/Glossary.md
diff --git a/docs/Location.md b/docs/Location.md
@@ -1,6 +1,6 @@
 ## Location
 
-A [`location` object](Terms.md#location) is conceptually similar to [`document.location` in web browsers](https://developer.mozilla.org/en-US/docs/Web/API/Document/location), with a few extra goodies. `location` objects have the following properties:
+A [`location` object](Glossary.md#location) is conceptually similar to [`document.location` in web browsers](https://developer.mozilla.org/en-US/docs/Web/API/Document/location), with a few extra goodies. `location` objects have the following properties:
 
 ```
 pathname      The pathname portion of the URL, without query string

diff --git a/docs/QuerySupport.md b/docs/QuerySupport.md
@@ -1,6 +1,6 @@
 ## Query Support
 
-Support for parsing and serializing [URL queries](Terms.md#query) is provided by the `useQueries` [enhancer](Terms.md#createhistoryenhancer) function. Simply use a wrapped version of your `createHistory` function to create your `history` object and you'll have a parsed `location.query` object inside `listen` and `listenBefore` callbacks.
+Support for parsing and serializing [URL queries](Glossary.md#query) is provided by the `useQueries` [enhancer](Glossary.md#createhistoryenhancer) function. Simply use a wrapped version of your `createHistory` function to create your `history` object and you'll have a parsed `location.query` object inside `listen` and `listenBefore` callbacks.
 
 ```js
 import { createHistory, useQueries } from 'history'

diff --git a/docs/README.md b/docs/README.md
@@ -6,4 +6,4 @@
 - [Query Support](QuerySupport.md)
 - [Basename Support](BasenameSupport.md)
 - [Caveats of Using Hash History](HashHistoryCaveats.md)
-- [Glossary](Terms.md)
+- [Glossary](Glossary.md)