Fix some typo in readme
This commit is contained in:
parent
b1b4dc4e71
commit
10ad4d8b4c
12
README.md
12
README.md
|
@ -91,8 +91,8 @@
|
||||||
|
|
||||||
`Spacemacs` is a user-friendly and well-documented Emacs Advanced kit.
|
`Spacemacs` is a user-friendly and well-documented Emacs Advanced kit.
|
||||||
|
|
||||||
`Advanced` means here that it heavily and happily perform non-trivial tweaks
|
`Advanced` means here that it heavily and happily performs non-trivial tweaks
|
||||||
and customization in order to make it easy to use and unique.
|
and customization in order to make itself easy to use and unique.
|
||||||
|
|
||||||
`Advanced` does not mean that you have to be an advanced Emacs user, beginners
|
`Advanced` does not mean that you have to be an advanced Emacs user, beginners
|
||||||
are welcome and encouraged to use `Spacemacs` since it provides a simple
|
are welcome and encouraged to use `Spacemacs` since it provides a simple
|
||||||
|
@ -124,7 +124,7 @@ what matters: your text files.
|
||||||
- **Mnemonic and consistent key bindings** which should be easier to learn
|
- **Mnemonic and consistent key bindings** which should be easier to learn
|
||||||
and remember.
|
and remember.
|
||||||
|
|
||||||
- **Fast boot time**, some time has been invested to make 'Spacemacs' quick
|
- **Fast boot time**, some time has been invested to make `Spacemacs` quick
|
||||||
to load.
|
to load.
|
||||||
|
|
||||||
- **Lower the risk of RSI** by using the space key as much as possible.
|
- **Lower the risk of RSI** by using the space key as much as possible.
|
||||||
|
@ -207,9 +207,7 @@ keybindings.el | Emacs built-in key bindings or mandatory key bindings
|
||||||
packages.el | The list of packages to install and the functions to initialize them
|
packages.el | The list of packages to install and the functions to initialize them
|
||||||
|
|
||||||
`Packages` are `ELPA` packages which can be installed from an `ELPA` compliant
|
`Packages` are `ELPA` packages which can be installed from an `ELPA` compliant
|
||||||
repository, and `Extensions` are elisp code from git submodules, they can also
|
repository, and `Extensions` are generally elisp code from git submodules.
|
||||||
be directly stored in this git repository (maybe we call this: site elisp
|
|
||||||
code ??).
|
|
||||||
|
|
||||||
### Extensions and Packages initialization
|
### Extensions and Packages initialization
|
||||||
|
|
||||||
|
@ -219,7 +217,7 @@ name. `Pre-Extensions` are loaded before `Packages` and `Post-Extensions` are
|
||||||
loaded after `Packages`.
|
loaded after `Packages`.
|
||||||
|
|
||||||
They are processed in alphabetical order so sometimes you'll have to use
|
They are processed in alphabetical order so sometimes you'll have to use
|
||||||
some `after-eval-load` black magic.
|
some `eval-after-load` black magic.
|
||||||
|
|
||||||
To initialize an extension or a package `xxx`, define a function with this
|
To initialize an extension or a package `xxx`, define a function with this
|
||||||
format in `extensions.el` or `packages.el`:
|
format in `extensions.el` or `packages.el`:
|
||||||
|
|
Loading…
Reference in a new issue