Blob Blame History Raw
From 1a7c313db4a96319d1a02774846882982b39da40 Mon Sep 17 00:00:00 2001
Message-Id: <1a7c313db4a96319d1a02774846882982b39da40.1377873642.git.jdenemar@redhat.com>
From: Michal Privoznik <mprivozn@redhat.com>
Date: Mon, 26 Aug 2013 17:41:47 +0200
Subject: [PATCH] docs: Clean 09adfdc62de2b up

https://bugzilla.redhat.com/show_bug.cgi?id=1001143

(cherry picked from commit 8563b091fff4856a0cee7b568e52ff5b64d96ed3)
---
 docs/formatdomain.html.in | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in
index fb4238e..3fd83c9 100644
--- a/docs/formatdomain.html.in
+++ b/docs/formatdomain.html.in
@@ -677,8 +677,9 @@
       <dd> The optional <code>hard_limit</code> element is the maximum memory
         the guest can use. The units for this value are kibibytes (i.e. blocks
         of 1024 bytes). <strong>However, users of QEMU and KVM are strongly
-        advised not to set this limit as domain may get killed by the kernel.
-        To determine the memory needed for a process to run is
+        advised not to set this limit as domain may get killed by the kernel
+        if the guess is too low. To determine the memory needed for a process
+        to run is an
         <a href="http://en.wikipedia.org/wiki/Undecidable_problem">
         undecidable problem</a>.</strong></dd>
       <dt><code>soft_limit</code></dt>
-- 
1.8.3.2