remove old api-overview urls

Author: fratzinger

docs/common-patterns.md

@@ -174,42 +174,15 @@ in the above example of component code, the `upcomingAppointments` and `pastAppo
 
 ## Organizing the services in your project
 
-You can use the file system to organize each service into its own module. This is especially useful in organizing larger-sized projects.  Here's an example `store.js`.  It uses Webpack's require.context feature save repetitive imports:
+You can use the file system to organize each service into its own module. This is especially useful in organizing larger-sized projects.  Here's an example `store.js`.  It uses Webpack's require.context feature save repetitive imports.
 
-```js
-import Vue from 'vue'
-import Vuex from 'vuex'
-import { FeathersVuex } from '../feathers-client'
-import auth from './store.auth'
-
-Vue.use(Vuex)
-Vue.use(FeathersVuex)
-
-const requireModule = require.context(
-  // The path where the service modules live
-  './services',
-  // Whether to look in subfolders
-  false,
-  // Only include .js files (prevents duplicate imports`)
-  /.js$/
-)
-const servicePlugins = requireModule
-  .keys()
-  .map(modulePath => requireModule(modulePath).default)
-
-export default new Vuex.Store({
-  state: {},
-  mutations: {},
-  actions: {},
-  plugins: [...servicePlugins, auth]
-})
-```
+See it [here](/getting-started.html#auth-plugin)
 
 With the `store.js` file in place, we can start adding services to the `services` folder.
 
-- [Learn how to setup a Vuex plugin for a Feathers service.](/api-overview.html#service-plugins)
-- [Learn how to setup the feathers-client.js file](/api-overview.html)
-- [Learn how to setup the auth plugin](/api-overview.html#auth-plugin)
+- [Learn how to setup the feathers-client.js file](/getting-started.html#feathers-client-feathers-vuex)
+- [Learn how to setup a Vuex plugin for a Feathers service](/getting-started.html#service-plugins)
+- [Learn how to setup the auth plugin](/getting-started.html#auth-plugin)
 
 ## Actions return reactive store records
 

docs/model-classes.md

@@ -10,7 +10,7 @@ Feathers-Vuex 1.0 introduced some lightweight data modeling.  Every service had
 
 ## Extending the BaseModel Class
 
-While [setting up Feathers-Vuex](/api-overview.html#feathers-client-feathers-vuex), we exported the `BaseModel` class so that we could extend it.  The below example shows how to import and extend the `BaseModel`.  Each service must now have its own unique Model class.
+While [setting up Feathers-Vuex](/getting-started.html#feathers-client-feathers-vuex), we exported the `BaseModel` class so that we could extend it.  The below example shows how to import and extend the `BaseModel`.  Each service must now have its own unique Model class.
 
 ```js
 import feathersClient, { makeServicePlugin, BaseModel } from '../feathers-client'

docs/nuxt.md

@@ -16,7 +16,7 @@ The `models` and `$FeathersVuex` variables are the same object.
 
 ## Preventing Memory Leaks
 
-The default settings of Feathers-Vuex include having realtime events enabled by default.  This will result in increased memory usage over time on the SSR server.  It can be turned off when you configure `feathers-vuex`.  The example below has been modified from the example of [Setting up the Feathers Client & Feathers-Vuex](./api-overview.md#feathers-client-feathers-vuex).  Look specifically at the `enableEvents` option.
+The default settings of Feathers-Vuex include having realtime events enabled by default.  This will result in increased memory usage over time on the SSR server.  It can be turned off when you configure `feathers-vuex`.  The example below has been modified from the example of [Setting up the Feathers Client & Feathers-Vuex](./getting-started.html#feathers-client-feathers-vuex).  Look specifically at the `enableEvents` option.
 
 ```js
 const { makeServicePlugin, makeAuthPlugin, BaseModel, models, FeathersVuex } = feathersVuex(