From: Michael Stapelberg Date: Sat, 25 Dec 2010 14:42:53 +0000 (+0100) Subject: s/separate/seperate/g (Thanks Donald) X-Git-Tag: 4.0~24 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=2959dcb24c26a18aedba3111890b34eba93f216b;p=i3%2Fi3 s/separate/seperate/g (Thanks Donald) --- diff --git a/docs/debugging b/docs/debugging index d52edea9..b4bda670 100644 --- a/docs/debugging +++ b/docs/debugging @@ -14,7 +14,7 @@ debugging and/or need further help, do not hesitate to contact us! i3 spits out much information onto stdout, if told so. To have a clearly defined place where log files will be saved, you should redirect stdout and -stderr in xsession. While you’re at it, putting each run of i3 in a separate +stderr in xsession. While you’re at it, putting each run of i3 in a seperate log file with date/time in it is a good idea to not get confused about the different log files later on. diff --git a/docs/hacking-howto b/docs/hacking-howto index dff074cb..8a778546 100644 --- a/docs/hacking-howto +++ b/docs/hacking-howto @@ -216,7 +216,7 @@ screen you are currently on. A workspace is identified by its number. Basically, you could think of workspaces as different desks in your office, if you like the desktop methaphor. They just contain different sets of windows and are completely -separate of each other. Other window managers also call this ``Virtual +seperate of each other. Other window managers also call this ``Virtual desktops''. === The layout table @@ -264,7 +264,7 @@ should be chosen for those: == Startup (src/mainx.c, main()) * Establish the xcb connection - * Check for XKB extension on the separate X connection + * Check for XKB extension on the seperate X connection * Check for Xinerama screens * Grab the keycodes for which bindings exist * Manage all existing windows diff --git a/docs/ipc b/docs/ipc index 5fcaf62e..c35e9016 100644 --- a/docs/ipc +++ b/docs/ipc @@ -3,7 +3,7 @@ IPC interface (interprocess communication) Michael Stapelberg March 2010 -This document describes how to interface with i3 from a separate process. This +This document describes how to interface with i3 from a seperate process. This is useful for example to remote-control i3 (to write test cases for example) or to get various information like the current workspaces to implement an external workspace bar. @@ -241,7 +241,7 @@ situation can happen: You send a GET_WORKSPACES request but you receive a "workspace" event before receiving the reply to GET_WORKSPACES. If your program does not want to cope which such kinds of race conditions (an event based library may not have a problem here), I suggest you create a -separate connection to receive events. +seperate connection to receive events. === Subscribing to events diff --git a/docs/userguide b/docs/userguide index f3d71fcd..7402f64b 100644 --- a/docs/userguide +++ b/docs/userguide @@ -556,7 +556,7 @@ simple -- it does not provide a way to display custom text and it does not offer advanced customization features. This is intended because we do not want to duplicate functionality of tools like +dzen2+, +xmobar+ and so on (they render bars, we manage windows). Instead, there is an option which will -turn off the internal bar completely, so that you can use a separate program to +turn off the internal bar completely, so that you can use a seperate program to display it (see +i3-wsbar+, a sample implementation of such a program): *Syntax*: