From 530e64e9ec9755af34c3fd7d24ef7a287fe0dd5a Mon Sep 17 00:00:00 2001 From: Enric Morales Date: Fri, 16 Dec 2016 22:02:35 +0100 Subject: [PATCH] Fix more typos --- docs/03-declarative-layout.md | 10 +++++----- docs/05-awesomerc.md.lua | 2 +- docs/16-using-cairo.md | 4 ++-- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/03-declarative-layout.md b/docs/03-declarative-layout.md index 2e49f207f..c0b34e5b9 100644 --- a/docs/03-declarative-layout.md +++ b/docs/03-declarative-layout.md @@ -17,7 +17,7 @@ Awesome provides 2 collections of widgets: ### Containers -A container is a widgets that wraps another widget. It can be used to add +A container is a widget that wraps another widget. It can be used to add decorations or to modify the content of the child widget. @DOC_container_WIDGET_LIST@ @@ -109,7 +109,7 @@ Result: ### Use a `wibox.layout.align` layout The `wibox.layout.align` is a little different. While most layouts will ignore any `nil` lines, the `align` layout relies on them so `left`, `middle` -and `right` can be defined +and `right` can be defined. Code: @@ -177,7 +177,7 @@ Code: ### Accessing widgets For each widget or container, it is possible to add an `identifier` attribute -so that it accessed later. +so that it can be accessed later. Widgets defined using `setup` can be accessed using these methods: @@ -191,10 +191,10 @@ the chain has a valid identifier. The last one doesn't require long paths, but it is not easy to get a specific instance if multiple widgets have the same identifier. -WARNING: The widget identifier must not use reserved name. This includes all +WARNING: The widget identifier must not use a reserved name. This includes all method names, existing widget attributes, `layout` and `widget`. Names should also respect the Lua variable conventions (case-sensitive, alphanumeric, -underscore characters and non-numeric first character) +underscore characters and non-numeric first character). Code: diff --git a/docs/05-awesomerc.md.lua b/docs/05-awesomerc.md.lua index ee9ec8966..139dfb817 100644 --- a/docs/05-awesomerc.md.lua +++ b/docs/05-awesomerc.md.lua @@ -46,7 +46,7 @@ non-exhaustive list of possible errors: the best way to debug this is either using `print()` or using `gdb`. For this, see the [Debugging tips Readme section](../documentation/01-readme.md.html) * Deprecated APIs: The Awesome API is not frozen for eternity. After a decade - of development and recent changes to enforce consistency, it doesn't hasn't + of development and recent changes to enforce consistency, it hasn't changed much. This doesn't mean it won't change in the future. Whenever possible, changes won't cause errors but will instead print a deprecation message in the Awesome logs. These logs are placed in various places diff --git a/docs/16-using-cairo.md b/docs/16-using-cairo.md index dbccd6487..e2f5329b1 100644 --- a/docs/16-using-cairo.md +++ b/docs/16-using-cairo.md @@ -1,7 +1,7 @@ # Using Cairo and LGI -These days, Awesome interface is mostly based on a library called LGI. It provides -access C libraries such as GTK, GLib, Cairo, Pango, PangoCairo and RSVG using +These days, Awesome's interface is mostly based on a library called LGI. It provides +access to C libraries such as GTK, GLib, Cairo, Pango, PangoCairo and RSVG using Lua code without having to write actual "glue" C code. This is done using the GObject-introspection framework. The main advantage is