aurora git commit: AURORA-1656 Fix broken links in tier documentation

[ma...@apache.org]

Repository: aurora
Updated Branches:
  refs/heads/master 4d7730bc4 -> 90846640b


AURORA-1656 Fix broken links in tier documentation

Bugs closed: AURORA-1656

Reviewed at https://reviews.apache.org/r/50902/


Project: http://git-wip-us.apache.org/repos/asf/aurora/repo
Commit: http://git-wip-us.apache.org/repos/asf/aurora/commit/90846640
Tree: http://git-wip-us.apache.org/repos/asf/aurora/tree/90846640
Diff: http://git-wip-us.apache.org/repos/asf/aurora/diff/90846640

Branch: refs/heads/master
Commit: 90846640bfc0e028df7818d503c3e82ba1609ea8
Parents: 4d7730b
Author: Mehrdad Nurolahzade <me...@nurolahzade.com>
Authored: Wed Aug 10 12:36:53 2016 -0700
Committer: Maxim Khutornenko <ma...@apache.org>
Committed: Wed Aug 10 12:36:53 2016 -0700

----------------------------------------------------------------------
 docs/features/multitenancy.md   | 4 ++--
 docs/reference/configuration.md | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/aurora/blob/90846640/docs/features/multitenancy.md
----------------------------------------------------------------------
diff --git a/docs/features/multitenancy.md b/docs/features/multitenancy.md
index 417c433..cb45beb 100644
--- a/docs/features/multitenancy.md
+++ b/docs/features/multitenancy.md
@@ -40,11 +40,11 @@ Configuration Tiers
 Tier is a predefined bundle of task configuration options. Aurora schedules tasks and assigns them
 resources based on their tier assignment. The default scheduler tier configuration allows for
 3 tiers:
- - `revocable`: The `revocable` tier requires the task to run with [revocable](../resource-isolation/#oversubscription)
+ - `revocable`: The `revocable` tier requires the task to run with [revocable](resource-isolation.md#oversubscription)
  resources.
  - `preemptible`: Setting the task\u2019s tier to `preemptible` allows for the possibility of that task
  being [preempted](#preemption) by other tasks when cluster is running low on resources.
- - `preferred`: The `preferred` tier prevents the task from using [revocable](../resource-isolation/#oversubscription)
+ - `preferred`: The `preferred` tier prevents the task from using [revocable](resource-isolation.md#oversubscription)
  resources and from being [preempted](#preemption).
 
 Since it is possible that a cluster is configured with a custom tier configuration, users should

http://git-wip-us.apache.org/repos/asf/aurora/blob/90846640/docs/reference/configuration.md
----------------------------------------------------------------------
diff --git a/docs/reference/configuration.md b/docs/reference/configuration.md
index 16b31be..ff40262 100644
--- a/docs/reference/configuration.md
+++ b/docs/reference/configuration.md
@@ -353,7 +353,7 @@ Job Schema
   ```health_check_config``` | ```HealthCheckConfig``` object | Parameters for controlling a task's health checks. HTTP health check is only used if a  health port was assigned with a command line wildcard.
   ```container``` | Choice of ```Container```, ```Docker``` or ```Mesos``` object | An optional container to run all processes inside of.
   ```lifecycle``` | ```LifecycleConfig``` object | An optional task lifecycle configuration that dictates commands to be executed on startup/teardown.  HTTP lifecycle is enabled by default if the "health" port is requested.  See [LifecycleConfig Objects](#lifecycleconfig-objects) for more information.
-  ```tier``` | String | Task tier type. The default scheduler tier configuration allows for 3 tiers: `revocable`, `preemptible`, and `preferred`. If a tier is not elected, Aurora assigns the task to a tier based on its choice of `production` (that is `preferred` for production and `preemptible` for non-production jobs). See the section on [Configuration Tiers](../features/multitenancy#configuration-tiers) for more information.
+  ```tier``` | String | Task tier type. The default scheduler tier configuration allows for 3 tiers: `revocable`, `preemptible`, and `preferred`. If a tier is not elected, Aurora assigns the task to a tier based on its choice of `production` (that is `preferred` for production and `preemptible` for non-production jobs). See the section on [Configuration Tiers](../features/multitenancy.md#configuration-tiers) for more information.
   ```announce``` | ```Announcer``` object | Optionally enable Zookeeper ServerSet announcements. See [Announcer Objects] for more information.
   ```enable_hooks``` | Boolean | Whether to enable [Client Hooks](client-hooks.md) for this job. (Default: False)