openstack
/
barbican
Code Issues Proposed changes

Imported Translations from Zanata 

For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html

Change-Id: I358a432957a820566569cfe27f7e13d1fa096392
This commit is contained in:
OpenStack Proposal Bot 2018-02-14 07:27:54 +00:00
parent 5b525f6b0a
commit 0a6a25bb82
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po
View File

@ -4,11 +4,11 @@ msgid ""
msgstr ""
"Project-Id-Version: Barbican Release Notes\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-02-09 17:50+0000\n"
"POT-Creation-Date: 2018-02-13 01:12+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2018-01-30 02:34+0000\n"
"PO-Revision-Date: 2018-02-13 11:56+0000\n"
"Last-Translator: Andi Chandler <andi@gowling.com>\n"
"Language-Team: English (United Kingdom)\n"
"Language: en-GB\n"
@ -288,7 +288,7 @@ msgstr ""
msgid ""
"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. While you will not be able 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."