From e4d20d581bf5fcac2e5e50dc4e085156bb8f7262 Mon Sep 17 00:00:00 2001 From: melissaml Date: Thu, 8 Feb 2018 00:44:24 +0800 Subject: [PATCH] Modify grammatical errors Change-Id: I8d1ed77f83fb9620127c77fdc87514fe38ead4de --- specs/juno/add-certificate-to-the-container-type.rst | 2 +- specs/kilo/add-creator-only-option.rst | 2 +- specs/kilo/barbican-mkek-model.rst | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/specs/juno/add-certificate-to-the-container-type.rst b/specs/juno/add-certificate-to-the-container-type.rst index 7b1330b..e7c485b 100644 --- a/specs/juno/add-certificate-to-the-container-type.rst +++ b/specs/juno/add-certificate-to-the-container-type.rst @@ -27,7 +27,7 @@ not be distinguishable. Proposed Change =============== -Add the `certificate` option for containers. This augments the the current type attribute on the containers resource and data model to accept `certificate` as a valid option. +Add the `certificate` option for containers. This augments the current type attribute on the containers resource and data model to accept `certificate` as a valid option. Alternatives ------------ diff --git a/specs/kilo/add-creator-only-option.rst b/specs/kilo/add-creator-only-option.rst index c71cd5a..e5ce20b 100644 --- a/specs/kilo/add-creator-only-option.rst +++ b/specs/kilo/add-creator-only-option.rst @@ -14,7 +14,7 @@ Problem Description ------------------- This is a companion spec to the add-per-secret-policy spec. That spec proposed -a mechanism for allowing users outside the the secrets project to access a +a mechanism for allowing users outside the secrets project to access a secret/container. This mechanism involved storing access control data in the database for each secret/container. diff --git a/specs/kilo/barbican-mkek-model.rst b/specs/kilo/barbican-mkek-model.rst index 1bce2c3..f59cc5b 100644 --- a/specs/kilo/barbican-mkek-model.rst +++ b/specs/kilo/barbican-mkek-model.rst @@ -91,7 +91,7 @@ provide its reference to the MKEK as the wrapping key so the HSM may unwrap it. An unwrapped DEK, provided by the project, will be sent to the HSM and then retrieved, wrapped by the projects KEK. This wrapped DEK will be stored in the local Barbican database. The unwrapped DEK and KEK will now be removed from the -HSM. This logic will placed within the the encrypt() interface method. +HSM. This logic will placed within the encrypt() interface method. Project Data Encryption Key (DEK) retrieval. A project wrapped DEK (its encrypted secret) will be retrieved from Barbican's