aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/08_Preferences.md10
-rw-r--r--doc/14_Appendix.md6
2 files changed, 8 insertions, 8 deletions
diff --git a/doc/08_Preferences.md b/doc/08_Preferences.md
index f57e02ca..efcd1fb5 100644
--- a/doc/08_Preferences.md
+++ b/doc/08_Preferences.md
@@ -9,9 +9,9 @@ At this point the manual assumes you are at least familiar with the basics of
Textadept executes a *~/.textadept/init.lua*, your user-init file, on startup.
If this file does not exist, Textadept creates it for you. This file allows you
-to indicate what you want Textadept to do when the application starts, such as
-change the settings of existing modules, load new ones, and/or run plain Lua
-code.
+to indicate what you want Textadept to do when the application starts. Examples
+include changing the settings of existing modules, loading new modules, and
+running arbitrary Lua code.
### Modules
@@ -155,8 +155,8 @@ from *~/.textadept/init.lua*. For example:
## Buffer Properties
Since Textadept runs *~/.textadept/init.lua* only once on startup, it is not the
-appropriate place to set per-buffer properties like indentation size or
-view-related properties like the behaviors for scrolling and autocompletion.
+appropriate place to set per-buffer properties (like indentation size) or
+view-related properties (like the behaviors for scrolling and autocompletion).
If you do set such properties in *~/.textadept/init.lua*, those settings only
apply to the first buffer and view -- subsequent buffers and split views will
not inherit those settings. Instead, put your settings in a
diff --git a/doc/14_Appendix.md b/doc/14_Appendix.md
index e128143b..182569cf 100644
--- a/doc/14_Appendix.md
+++ b/doc/14_Appendix.md
@@ -128,9 +128,9 @@ non-existant graphics capabilities:
(`0xFF0000`), light green (`0x00FF00`), light yellow (`0xFFFF00`), light blue
(`0x0000FF`), light magenta (`0xFF00FF`), light cyan (`0x00FFFF`), and light
white (`0xFFFFFF`). Even if your terminal uses a different color map, you must
- use these color values; unrecognized colors default to white. For some
- terminals, you may need to set a lexer style's `bold` attribute to use the
- light color variant.
+ use these color values. Your terminal will remap them automatically.
+ Unrecognized colors default to white. For some terminals, you may need to set
+ a lexer style's `bold` attribute to use the light color variant.
* No scroll bars.
* Not all key sequences recognized properly.
* No style settings like font name, font size, or italics.