diff options
| author | j3parker <j3parker@csclub.uwaterloo.ca> | 2010-11-21 15:00:16 -0500 |
|---|---|---|
| committer | Kristian Høgsberg <krh@bitplanet.net> | 2010-11-22 10:34:22 -0500 |
| commit | 45d574243269b1f52ad87c4f601a70050a1f0541 (patch) | |
| tree | 15d89a892a8637512fb480523cd4348d3eb03568 | |
| parent | b4963a7927e137ba45d8cccd64f2a9556c9c3add (diff) | |
typos in faq
| -rw-r--r-- | faq.html | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -93,7 +93,7 @@ <h3>Why not extend the X server?</h3> <p> - Because we for the first time we have a realistic chance of not + Because for the first time we have a realistic chance of not having to do that. It's entirely possible to incorporate the buffer exchange and update models that Wayland is built on into X. However, we have an option here of pushing X out of the hotpath @@ -115,7 +115,7 @@ The problem with X is that... it's X. When you're an X server there's a tremendous amount of functionality that you must support to claim to speak the X protocol, yet nobody will ever use this. - For example core fonts; this is the original font model that was how + For example, core fonts; this is the original font model that was how your got text on the screen for the many first years of X11. This includes code tables, glyph rasterization and caching, XLFDs (seriously, XLFDs!) Also, the entire core rendering API that lets |