From 5e315ac96e7dd10e64ce7102ab10415daf2f7782 Mon Sep 17 00:00:00 2001
From: Darragh O'Reilly <dara2002-openstack@yahoo.com>
Date: Mon, 28 Oct 2013 07:53:14 +0000
Subject: [PATCH] Correct the libvirt_inject_partition flag

The instructions to disable libvirt file injection had the flag misspelled.

Change-Id: I975fa2c745468cca4325aff9ceca7665cb329779
Closes-Bug: 1245364
---
 doc/common/section_support-compute.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/common/section_support-compute.xml b/doc/common/section_support-compute.xml
index 5ee1b8a818..786f0d0743 100644
--- a/doc/common/section_support-compute.xml
+++ b/doc/common/section_support-compute.xml
@@ -135,7 +135,7 @@
        <title>Problems with injection</title>
        <para>If you are diagnosing problems with instances not booting,
        or booting slowly, consider investigating file injection as a
-       cause. Setting <literal>libvirt_injection_partition</literal>
+       cause. Setting <literal>libvirt_inject_partition</literal>
        to -2 disables injection in libvirt. This can be required if you want to make user
        specified files available from the metadata server (and config drive is not enabled),
        for performance reasons, and also to avoid boot failure if injection itself fails.</para>