[elpa] externals/sql-indent 3ee7f95 08/13: Fix various typos here and there. (#57)

[Stefan Monnier]

branch: externals/sql-indent
commit 3ee7f9582c6b333a2499a3935efe7b93d79b869b
Author: Pierre Téchoueyres <address@hidden>
Commit: Alex Harsányi <address@hidden>

    Fix various typos here and there. (#57)
---
 README.md          |  2 +-
 sql-indent-left.el |  4 ++--
 sql-indent-test.el | 10 +++++-----
 sql-indent.org     |  4 ++--
 4 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/README.md b/README.md
index e10075c..4351078 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
 
 [![Build 
Status](https://travis-ci.org/alex-hhh/emacs-sql-indent.svg?branch=master)](https://travis-ci.org/alex-hhh/emacs-sql-indent)
 
-sql-indnent.el is a GNU Emacs minor mode which adds support for syntax-based
+sql-indent.el is a GNU Emacs minor mode which adds support for syntax-based
 indentation when editing SQL code: TAB indents the current line based on the
 syntax of the SQL code on previous lines.  This works like the indentation for
 C and C++ code.
diff --git a/sql-indent-left.el b/sql-indent-left.el
index b0fac9e..42cbf25 100644
--- a/sql-indent-left.el
+++ b/sql-indent-left.el
@@ -197,8 +197,8 @@ select aaa,
     (nested-statement-open         1)
     (nested-statement-continuation 1)
     (nested-statement-close        sqlind-use-anchor-indentation)
-    (string-continuation 0) ;; or shoult it be a begining of line or aligned 
with the previous block ?
-                            ;; Anyway. It's really *BAD* to continue a string 
accross lines.
+    (string-continuation 0) ;; or should it be a beginning of line or aligned 
with the previous block ?
+                            ;; Anyway. It's really *BAD* to continue a string 
across lines.
     (select-column sqlind-indent-select-column-alt
                   sqlind-adjust-operator
                   sqlind-lone-semicolon)
diff --git a/sql-indent-test.el b/sql-indent-test.el
index cb91d30..8361be2 100644
--- a/sql-indent-test.el
+++ b/sql-indent-test.el
@@ -38,10 +38,10 @@
 ;;;; There are two types of tests,
 ;;
 ;; * SYNTAX CHECKS check if the syntax in an SQL file is correctly
-;;   indentified.  These tests are independent of indentation preferences (see
+;;   identified.  These tests are independent of indentation preferences (see
 ;;   `sqlind-ert-check-file-syntax')
 ;;
-;; * INDENTATION CHECKS checks if a file is indented corectly for a set of
+;; * INDENTATION CHECKS check if a file is indented correctly for a set of
 ;;   rules. (see `sqlind-ert-check-file-indentation')
 ;;
 ;; Both types of tests work by having a sample SQL file with syntax and
@@ -89,7 +89,7 @@
 ;;   test (as generated by `sqlind-collect-syntax-from-buffer')
 ;;
 ;; * "test-data/pr30-io-XXX.eld" -- contains the indentation offsets for the
-;;   indentation rules beging tested (where XXX is a short name for those
+;;   indentation rules being tested (where XXX is a short name for those
 ;;   rules)
 ;;
 ;; * `sqlind-ert-pr30' -- is the name of the test function in this file. If
@@ -142,7 +142,7 @@
   "Indent the buffer according to RULES and BASIC-OFFSET.
 The RULES and BASIC-OFFSET are installed as
 `sqlind-indentation-offsets-alist' and `sqlind-basic-offset' than
-inddent the whole buffer."
+indent the whole buffer."
   (when rules
     (setq sqlind-indentation-offsets-alist rules))
   (when basic-offset
@@ -181,7 +181,7 @@ function should be run a part of an ERT test."
 (defun sqlind-ert-check-file-syntax (sql-file data-file)
   "Check the syntax of each line in SQL-FILE.
 The syntax of each line in SQL-FILE is checked against the
-previously saved syntax data in DATA-FILE.  An error is signaled
+previously saved syntax data in DATA-FILE.  An error is signalled
 if there is a mismatch."
   (let ((syntax-data (sqlind-ert-read-data data-file)))
     (with-current-buffer (find-file sql-file)
diff --git a/sql-indent.org b/sql-indent.org
index f6d1cee..a2e1121 100644
--- a/sql-indent.org
+++ b/sql-indent.org
@@ -248,8 +248,8 @@ line
 
 **** sqlind-lineup-open-paren-to-anchor
 
-if the line starts with an open paren, discard the current offset and return
-the column of the anchor point.
+if the line starts with an open parenthesis, discard the current
+offset and return the column of the anchor point.
 
 **** sqlind-lone-semicolon