From cc6d614fcfc2b45b0f15139252540b2eb942ceca Mon Sep 17 00:00:00 2001 From: Shubham Singh Manhas Date: Fri, 26 Oct 2018 01:39:18 +0530 Subject: [PATCH] Update Readme.srt Fixed some typos. --- README.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.rst b/README.rst index 24e40e7..f6940a8 100644 --- a/README.rst +++ b/README.rst @@ -84,8 +84,8 @@ The key is passed in the Authorization header, prefixed by APIKey:: Authorization APIKey ZGJkYWI3ZmQtZDEwNy00MzJiLWJlNDgtMjZkNTQyZGFiZDhi -The value is a base64-encoded UUID. Each application that whishes to get a -priviledged access should have its own API key and scope. +The value is a base64-encoded UUID. Each application that wishes to get a +privileged access should have its own API key and scope. You can list/add/revoke keys using the **servicebook-keys** command:: @@ -109,7 +109,7 @@ You can list/add/revoke keys using the **servicebook-keys** command:: App: MyApp2, Key: e87271fd-ca31-46cf-8cc5-48b1f9348e4e, Scope: readwrite -The default setup will make the data read-only and will required a privileged +The default setup will make the data read-only and will require a privileged access with **readwrite** scope for writing in the database. You should have one separate key per calling service so it's easier to revoke or