[libvirt] [PATCH] formatdomain.html.in: Correctly use <code/> in #elementQoS

[Martin Kletzander]

On 07/26/2013 11:46 AM, Michal Privoznik wrote:
> Interestingly, we had <code>floor<code> ... </code>outbound</code> which
> results in much larger block of text to be written in code style that
> intended.
> ---
>  docs/formatdomain.html.in | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in
> index 7601aaa..d2cee67 100644
> --- a/docs/formatdomain.html.in
> +++ b/docs/formatdomain.html.in
> @@ -3539,12 +3539,12 @@ qemu-kvm -net nic,model=? /dev/null
>        forward type of route, nat, or no forward at all). Moreover, the
>        virtual network the interface is connected to is required to have at least
>        inbound QoS set (<code>average</code> at least). Moreover, with
> -      <code>floor<code> attribute users don't need to specify
> +      <code>floor</code> attribute users don't need to specify
>        <code>average</code>. However, <code>peak</code> and <code>burst</code>
>        attributes still require <code>average</code>. Currently, linux kernel
>        doesn't allow ingress qdiscs to have any classes therefore
>        <code>floor</code> can be applied only on <code>inbound</code> and not
> -      </code>outbound</code>. <span class="since">Since 1.0.1</span>
> +      <code>outbound</code>. <span class="since">Since 1.0.1</span>
>      </p>
>  
>      <h5><a name="elementVlanTag">Setting VLAN tag (on supported network types only)</a></h5>
> 

ACK, trivial.

Martin