Imported Translations from Transifex

Change-Id: I07736873c23ba5b35aa30b1edbd6ebb854e6c2e6

doc/admin-guide-cloud/locale/admin-guide-cloud.pot

@@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2014-10-10 06:40+0000\n"
+"POT-Creation-Date: 2014-10-14 07:23+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -8599,7 +8599,7 @@ msgid "Trustee"
 msgstr ""
 
 #: ./doc/admin-guide-cloud/identity/section_keystone-trusts.xml:21(para)
-msgid "The user the trust is being delegated to, for a limited time."
+msgid "The user trust is being delegated to, for a limited time."
 msgstr ""
 
 #: ./doc/admin-guide-cloud/identity/section_keystone-trusts.xml:25(para)

doc/arch-design/locale/arch-design.pot

@@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2014-09-26 06:09+0000\n"
+"POT-Creation-Date: 2014-10-14 07:23+0000\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -3610,7 +3610,7 @@ msgid "It is important to first understand additional factors as well as the use
 msgstr ""
 
 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:348(para)
-msgid "It is recommended that the network architecture is designed using a scalable network model that makes it easy to add capacity and bandwidth. A good example of such a model is the leaf-spline model. In this type of network design, it is possible to easily add additional bandwidth as well as scale out to additional racks of gear. It is important to select network hardware that will support the required port count, port speed and port density while also allowing for future growth as workload demands increase. It is also important to evaluate where in the network architecture it is valuable to provide redundancy. Increased network availability and redundancy comes at a cost, therefore it is recommended to weigh the cost versus the benefit gained from utilizing and deploying redundant network switches and using bonded interfaces at the host level."
+msgid "We recommend designing the network architecture using a scalable network model that makes it easy to add capacity and bandwidth. A good example of such a model is the leaf-spline model. In this type of network design, it is possible to easily add additional bandwidth as well as scale out to additional racks of gear. It is important to select network hardware that will support the required port count, port speed and port density while also allowing for future growth as workload demands increase. It is also important to evaluate where in the network architecture it is valuable to provide redundancy. Increased network availability and redundancy comes at a cost, therefore we recommend to weigh the cost versus the benefit gained from utilizing and deploying redundant network switches and using bonded interfaces at the host level."
 msgstr ""
 
 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:364(para)
@@ -3710,7 +3710,7 @@ msgid "If any of these software packages are needed, then the design must accoun
 msgstr ""
 
 #: ./doc/arch-design/compute_focus/section_architecture_compute_focus.xml:590(para)
-msgid "A large majority of the OpenStack components require access to back-end database services to store state and configuration information. Selection of an appropriate back-end database that will satisfy the availability and fault tolerance requirements of the OpenStack services is required. OpenStack services support connecting to any database that is supported by the SQLAlchemy Python drivers, however most common database deployments make use of MySQL or some variation of it. It is recommended that the database which provides back-end service within a general purpose cloud be made highly available using an available technology which can accomplish that goal. Some of the more common software solutions used include Galera, MariaDB and MySQL with multi-master replication."
+msgid "A large majority of the OpenStack components require access to back-end database services to store state and configuration information. Selection of an appropriate back-end database that will satisfy the availability and fault tolerance requirements of the OpenStack services is required. OpenStack services support connecting to any database that is supported by the SQLAlchemy Python drivers, however most common database deployments make use of MySQL or some variation of it. We recommend that the database which provides back-end service within a general purpose cloud be made highly available using an available technology which can accomplish that goal. Some of the more common software solutions used include Galera, MariaDB and MySQL with multi-master replication."
 msgstr ""
 
 #. When image changes, this message will be marked fuzzy or untranslated for you.