Repository: mesos
Updated Branches:
  refs/heads/master 48be0da27 -> feaa23649


Removed non-ASCII chars in authorisation.md.


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

Branch: refs/heads/master
Commit: feaa2364999d5f6c7125fd9c47deac33b468bb93
Parents: 48be0da
Author: Alexander Rukletsov <[email protected]>
Authored: Tue Mar 28 22:12:29 2017 +0200
Committer: Alexander Rukletsov <[email protected]>
Committed: Tue Mar 28 22:12:29 2017 +0200

----------------------------------------------------------------------
 docs/authorization.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/mesos/blob/feaa2364/docs/authorization.md
----------------------------------------------------------------------
diff --git a/docs/authorization.md b/docs/authorization.md
index 5a5d23b..b019120 100644
--- a/docs/authorization.md
+++ b/docs/authorization.md
@@ -753,7 +753,7 @@ authorization interface consists of three parts:
 First, the `authorization::Request` protobuf message represents a request to be
 authorized. It follows the
 
_[Subject-Verb-Object](https://en.wikipedia.org/wiki/Subject%E2%80%93verb%E2%80%93object)_
-pattern, where a _subject_ — commonly a principal — attempts to perform an
+pattern, where a _subject_ ---commonly a principal---attempts to perform an
 _action_ on a given _object_.
 
 Second, the
@@ -798,8 +798,8 @@ one or more fields must be set
 (e.g., the `view_executors` action expects the `executor_info` and
 `framework_info` to be set).
 
-The `action` field of the `Request` message is an enum. It is kept optional —
-even though a valid action is necessary for every request — to allow for
+The `action` field of the `Request` message is an enum. It is kept optional---
+even though a valid action is necessary for every request---to allow for
 backwards compatibility when adding new fields (see
 [MESOS-4997](https://issues.apache.org/jira/browse/MESOS-4997) for details).
 

Reply via email to