From d5947515875d410d01dfb193aaaef173d4eec16f Mon Sep 17 00:00:00 2001
From: chenjiao <chenjiao@inspur.com>
Date: Tue, 23 Jan 2018 18:38:17 +0800
Subject: [PATCH] Authorites spelling error
Authorites should be Authorities
Change-Id: I48a7417630c748dddd46d0671543ade16bf1d971
---
.../notes/removing-cas-certificate-orders-96fc47a7acaea273.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/releasenotes/notes/removing-cas-certificate-orders-96fc47a7acaea273.yaml b/releasenotes/notes/removing-cas-certificate-orders-96fc47a7acaea273.yaml
index fc774d5f6..beaadd706 100644
--- a/releasenotes/notes/removing-cas-certificate-orders-96fc47a7acaea273.yaml
+++ b/releasenotes/notes/removing-cas-certificate-orders-96fc47a7acaea273.yaml
@@ -32,7 +32,7 @@ other:
- Will Barbican still be able to store Certificates?
Yes, absolutely! The only thing we're deprecating is the plugin
- interface that talks to Certificate Authorites and associated APIs.
+ interface that talks to Certificate Authorities and associated APIs.
While you will not be able to use Barbican to issue a new certificate,
you will always be able to securely store any certificates in Barbican,
including those issued by public CAs or internal CAs.