api-guide: fix the file injection considerations drift

When these docs were initially imported [1] the "Considerations"
section was after "Server personality" but [2] refactored the
latter and forgot about the former. This fixes that so
"Considerations" is now just nested into the "Server personality"
section.

[1] I6d5ba6b96772e0f17fc7484312222110ec103bbf
[2] Ibbffdb00d1529a386f338da4776eb614891731c8

Change-Id: Ife6acefd42b9b2f5910fe8f0b1b001eeec80ff06

1 files changed, 21 insertions, 22 deletions

diff --git a/api-guide/source/server_concepts.rst b/api-guide/source/server_concepts.rst
index 35fcefd8ae..1d1a139c6d 100644
--- a/api-guide/source/server_concepts.rst
+++ b/api-guide/source/server_concepts.rst
@@ -798,28 +798,6 @@ time. One or more networks can be specified. User can also specify a
 specific port on the network or the fixed IP address to assign to the
 server interface.
 
-Considerations
-~~~~~~~~~~~~~~
-
--  The maximum limit refers to the number of bytes in the decoded data
-   and not the number of characters in the encoded data.
-
--  The maximum number of file path/content pairs that you can supply is
-   also determined by the compute provider and is defined by the
-   maxPersonality absolute limit.
-
--  The absolute limit, maxPersonalitySize, is a byte limit that is
-   guaranteed to apply to all images in the deployment. Providers can
-   set additional per-image personality limits.
-
--  The file injection might not occur until after the server is built and
-   booted.
-
--  After file injection, personality files are accessible by only system
-   administrators. For example, on Linux, all files have root and the root
-   group as the owner and group owner, respectively, and allow user and
-   group read access only (octal 440).
-
 Server access addresses
 ~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -1090,3 +1068,24 @@ Follow these guidelines when you inject files:
 -  Encode the file contents as a Base64 string. The maximum size of the
    file contents is determined by the compute provider and may vary
    based on the image that is used to create the server.
+
+Considerations:
+
+-  The maximum limit refers to the number of bytes in the decoded data
+   and not the number of characters in the encoded data.
+
+-  The maximum number of file path/content pairs that you can supply is
+   also determined by the compute provider and is defined by the
+   maxPersonality absolute limit.
+
+-  The absolute limit, maxPersonalitySize, is a byte limit that is
+   guaranteed to apply to all images in the deployment. Providers can
+   set additional per-image personality limits.
+
+-  The file injection might not occur until after the server is built and
+   booted.
+
+-  After file injection, personality files are accessible by only system
+   administrators. For example, on Linux, all files have root and the root
+   group as the owner and group owner, respectively, and allow user and
+   group read access only (octal 440).