From 50ca8d30dee17e8f976b65fd1e89d62046a033a4 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Jo=C3=A3o=20T=C3=A1vora?= Date: Sun, 23 Nov 2014 12:23:15 +0000 Subject: [PATCH] Update README.mdown Fix misspellings --- README.mdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.mdown b/README.mdown index afe427750..75ca37a06 100644 --- a/README.mdown +++ b/README.mdown @@ -112,7 +112,7 @@ should be added like this to `yas-snippet-dirs`: # Manual, issues etc Please refer to the comprehensive [documentation][docs] for full -customization and support. If you find a bug in the code or in the +customisation and support. If you find a bug in the code or in the documentation, please report it on [the GitHub issue tracker][issues]. ## Important note regarding bug reporting @@ -123,7 +123,7 @@ The most important thing when reporting bugs is making sure that we have a way to reproduce the problem exactly like it happened to you. To do this, we need to rule out interference from external factors -like other Emacs extensions or your own customizations. +like other Emacs extensions or your own customisations. Here's an example report that "sandboxes" an Emacs session just for reproducing a bug. @@ -147,11 +147,11 @@ I can't get yasnippet to load because frankinbogen! ``` Using `emacs -Q` or temporarily moving your `.emacs` init file to the side -is another way to achieve good reproductability. +is another way to achieve good reproducibility. Here's a [another example](https://github.com/capitaomorte/yasnippet/issues/318) -of a bug report. It has everything needed for a sucessfull analysis +of a bug report. It has everything needed for a successful analysis and speedy resolution. Also, don't forget to state the Emacs version (use `M-x emacs-version`) and -- 2.39.2