From 3c6a124fa3c8569bebf6d573d2378ebe22aed296 Mon Sep 17 00:00:00 2001
From: Lance Bragstad <lbragstad@gmail.com>
Date: Wed, 26 Sep 2018 17:55:29 +0000
Subject: [PATCH] Update auto-provisioning example to use reader

The auto-provisioning documentation included an example for a
read-only role called observer. This work was done prior to the
default roles work done in Rocky. Let's update the reference to use
the canonicalized read-only term "reader" instead of "observer" for
the sake of presenting similar terminology everywhere.

Change-Id: I021ab6031e9fb18f0a1496759cf8fa36dd9c50ae
---
 .../advanced-topics/federation/mapping_combinations.rst       | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/source/advanced-topics/federation/mapping_combinations.rst b/doc/source/advanced-topics/federation/mapping_combinations.rst
index 4ce67fc222..6c37cf3ff1 100644
--- a/doc/source/advanced-topics/federation/mapping_combinations.rst
+++ b/doc/source/advanced-topics/federation/mapping_combinations.rst
@@ -755,7 +755,7 @@ For example, consider the following mapping:
                                 "name": "Production",
                                 "roles": [
                                     {
-                                        "name": "observer"
+                                        "name": "reader"
                                     }
                                 ]
                             },
@@ -796,7 +796,7 @@ authenticated and the mapping engine has applied values from the assertion
 and mapped them into the ``local`` rules.
 
 In the above example, an authenticated federated user will be granted the
-``observer`` role on the ``Production`` project, ``member`` role on the
+``reader`` role on the ``Production`` project, ``member`` role on the
 ``Staging`` project, and they will have ``admin`` role on the ``Project for
 jsmith``.