aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorMattias Andrée <maandree@operamail.com>2015-05-04 19:35:45 +0200
committerMattias Andrée <maandree@operamail.com>2015-05-04 19:35:45 +0200
commit2b6894868b3a3fe65232f2cf4e0bf395b1b32607 (patch)
treec344be3a7f120f2aa5613742486f40282bca492c /doc
parenttypo (diff)
downloadmds-2b6894868b3a3fe65232f2cf4e0bf395b1b32607.tar.gz
mds-2b6894868b3a3fe65232f2cf4e0bf395b1b32607.tar.bz2
mds-2b6894868b3a3fe65232f2cf4e0bf395b1b32607.tar.xz
typo
Signed-off-by: Mattias Andrée <maandree@operamail.com>
Diffstat (limited to '')
-rw-r--r--doc/info/mds.texinfo2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/info/mds.texinfo b/doc/info/mds.texinfo
index 42da451..c689806 100644
--- a/doc/info/mds.texinfo
+++ b/doc/info/mds.texinfo
@@ -8900,7 +8900,7 @@ that X's documentation.}
Wayland only has protocols for drawing onto a
buffer and input devices, and some very limited
output protocols. Wayland is inherently inflexible.
-If anyone was to add additional functionally must
+If anyone wants to add additional functionally must
do so in the compositor --- the window manager ---
and publish to protocol. It is then up to all
other compostors (window managers) to implement