mirror of
https://github.com/labwc/labwc.git
synced 2026-03-02 01:40:24 -05:00
Fix various typos across the codebase
This commit is contained in:
parent
60aab98e8d
commit
be37f9a564
21 changed files with 40 additions and 40 deletions
|
|
@ -61,7 +61,7 @@
|
|||
##
|
||||
## This allows xdg-desktop-portal-wlr to function (e.g. for screen-recording).
|
||||
## It is automatically set to "wlroots" by labwc though, so it is only
|
||||
## includeded here for completeness. Again, labwc will not over-write an
|
||||
## included here for completeness. Again, labwc will not over-write an
|
||||
## already set environment variable, so if you need it set to something else,
|
||||
## then uncomment and adjust.
|
||||
##
|
||||
|
|
|
|||
|
|
@ -355,7 +355,7 @@ extending outward from the snapped edge.
|
|||
|
||||
*<margin top="" bottom="" left="" right="" output="" />*
|
||||
Specify the number of pixels to reserve at the edges of an output
|
||||
(typically a dislay/screen/monitor). New, maximized and tiled windows
|
||||
(typically a display/screen/monitor). New, maximized and tiled windows
|
||||
will not be placed in these areas. The use-case for *<margin>* is as a
|
||||
workaround for clients such as panels that do NOT support the
|
||||
wlr-layer-shell protocol.
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ the `--exit` and `--reconfigure` options use.
|
|||
|
||||
# SESSION MANAGEMENT
|
||||
|
||||
To enable the use of graphical clients launched via D-Bus or systemd servie
|
||||
To enable the use of graphical clients launched via D-Bus or systemd service
|
||||
activation, labwc can update both activation environments on launch. Provided
|
||||
that labwc is aware of an active D-Bus user session (*i.e.*, the environment
|
||||
variable `DBUS_SESSION_BUS_ADDRESS` is defined), the compositor will invoke the
|
||||
|
|
|
|||
|
|
@ -423,7 +423,7 @@
|
|||
</mouse>
|
||||
|
||||
<!--
|
||||
A touch configuration can be bound to a specifc device. If device
|
||||
A touch configuration can be bound to a specific device. If device
|
||||
name is left empty, the touch configuration applies to all touch
|
||||
devices or functions as a fallback. Multiple touch configurations
|
||||
can exist.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue