Bug 56719 - (documentation) Section header is incorrectly formatted
Summary: (documentation) Section header is incorrectly formatted
Status: RESOLVED FIXED
Alias: None
Product: Wayland
Classification: Unclassified
Component: wayland (show other bugs)
Version: unspecified
Hardware: Other All
: low trivial
Assignee: Tiago Vignatti
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-03 15:41 UTC by Petr Gladkikh
Modified: 2012-11-13 20:49 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Petr Gladkikh 2012-11-03 15:41:16 UTC
Section header is formatted as plain text. Possible fix:

diff --git a/doc/Wayland/en_US/Architecture.xml b/doc/Wayland/en_US/Architecture.xml
index d5488b8..e688d63 100644
--- a/doc/Wayland/en_US/Architecture.xml
+++ b/doc/Wayland/en_US/Architecture.xml
@@ -263,8 +263,8 @@
       that even if an application passes a new buffer to the
       compositor, only a small part of the buffer may be
       different, like a blinking cursor or a spinner.
-      Hardware Enabling for Wayland
     </para>
+    <title>Hardware Enabling for Wayland</title>
     <para>
       Typically, hardware enabling includes modesetting/display
       and EGL/GLES2. On top of that Wayland needs a way to share
Comment 1 Tiago Vignatti 2012-11-06 19:16:41 UTC
I'm starting to check the documentation for the 1.0.1 now, so I already pushed in my local tree a slightly different fix (adding a new section instead). 

Thank you.
Comment 2 Kristian Høgsberg 2012-11-13 20:49:59 UTC
commit 73d845af941193c04c2451cea16f7500753e08b0
Author: Tiago Vignatti <tiago.vignatti@intel.com>
Date:   Tue Nov 6 17:17:01 2012 -0200

    doc: Fix incorrectly formatted section header
    
    https://bugs.freedesktop.org/show_bug.cgi?id=56719
    
    Reported-by: Petr Gladkikh <PetrGlad@gmail.com>
    Signed-off-by: Tiago Vignatti <tiago.vignatti@intel.com>


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.