[mesos] 01/02: Fixed anchor name in upgrades guide.

[bb...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

bbannier pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/mesos.git

commit 55028504b4c7ccd09de584d78334e9f00f411ae7
Author: Benjamin Bannier <bb...@apache.org>
AuthorDate: Sun Sep 1 16:57:37 2019 +0200

    Fixed anchor name in upgrades guide.
    
    Review: https://reviews.apache.org/r/71419
---
 docs/upgrades.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/upgrades.md b/docs/upgrades.md
index d745752..e630731 100644
--- a/docs/upgrades.md
+++ b/docs/upgrades.md
@@ -566,7 +566,7 @@ We categorize the changes as follows:
 
 * The `SET_QUOTA` and `REMOVE QUOTA` master calls are deprecated in favor of a new `UPDATE_QUOTA` master call.
 
-<a name="#1-9-x-quota-guarantees"></a>
+<a name="1-9-x-quota-guarantees"></a>
 
 * Prior to Mesos 1.9, the quota related APIs only exposed quota "guarantees" which ensured a minimum amount of resources would be available to a role. Setting guarantees also set implicit quota limits. In Mesos 1.9+, quota limits are now exposed directly.
   * Quota guarantees are now deprecated in favor of using only quota limits. Enforcement of quota guarantees required that Mesos holds back enough resources to meet all of the unsatisfied quota guarantees. Since Mesos is moving towards an optimistic offer model (to improve multi-role / multi- scheduler scalability, see MESOS-1607), it will become no longer possible to enforce quota guarantees by holding back resources. In such a model, quota limits are simple to enforce, but quota guaran [...]