aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorMattias Andrée <maandree@operamail.com>2015-05-04 19:41:10 +0200
committerMattias Andrée <maandree@operamail.com>2015-05-04 19:41:10 +0200
commit33bf4f7893bca7cf51d60c740e40c111f3764bd2 (patch)
treec40ffeebdbf46b9f206d068d74595b4ffa4af60d /doc
parenttypo (diff)
downloadmds-33bf4f7893bca7cf51d60c740e40c111f3764bd2.tar.gz
mds-33bf4f7893bca7cf51d60c740e40c111f3764bd2.tar.bz2
mds-33bf4f7893bca7cf51d60c740e40c111f3764bd2.tar.xz
typo
Signed-off-by: Mattias Andrée <maandree@operamail.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/info/mds.texinfo4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/info/mds.texinfo b/doc/info/mds.texinfo
index c689806..8b87da6 100644
--- a/doc/info/mds.texinfo
+++ b/doc/info/mds.texinfo
@@ -8900,9 +8900,9 @@ 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 wants 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
+and publish the protocol. It is then up to all
other compostors (window managers) to implement
the protocol.