Fix #57 - Lowercasing inline keywords in text and a few code samples that automatic script didn't handle. Fixed a few typos along the way.

Author: kibeha

docs/2-naming-conventions/naming-conventions.md

@@ -8,8 +8,8 @@
 4. Avoid long abbreviations. Abbreviations should be shorter than 5 characters.
 5. Any abbreviations must be widely known and accepted. 
 6. Create a glossary with all accepted abbreviations.
-7. Never use ORACLE keywords as names. A list of ORACLEs keywords may be found in the dictionary view `V$RESERVED_WORDS`.
-8. Avoid adding redundant or meaningless prefixes and suffixes to identifiers.<br/>Example: `CREATE TABLE emp_table`.
+7. Never use ORACLE keywords as names. A list of ORACLEs keywords may be found in the dictionary view `v$reserved_words`.
+8. Avoid adding redundant or meaningless prefixes and suffixes to identifiers.<br/>Example: `create table emp_table`.
 9. Always use one spoken language (e.g. English, German, French) for all objects in your application.
 10. Always use the same names for elements with the same meaning.
 

docs/3-coding-style/coding-style.md

@@ -9,7 +9,7 @@ Rule | Description
 1    | Keywords and names are written in lowercase[^2].
 2    | 3 space indention[^3].
 3    | One command per line.
-4    | Keywords `LOOP`, `ELSE`, `ELSIF`, `END IF`, `WHEN` on a new line.
+4    | Keywords `loop`, `else`, `elsif`, `end if`, `when` on a new line.
 5    | Commas in front of separated elements.
 6    | Call parameters aligned, operators aligned, values aligned.
 7    | SQL keywords are right aligned within a SQL command.

docs/4-language-usage/1-general/g-1020.md

@@ -8,7 +8,7 @@
 Use a label directly in front of loops and nested anonymous blocks:
 
 * To give a name to that portion of code and thereby self-document what it is doing.
-* So that you can repeat that name with the END statement of that block or loop.
+* So that you can repeat that name with the `end` statement of that block or loop.
 
 ## Example (bad)
 

docs/4-language-usage/1-general/g-1060.md

@@ -5,9 +5,9 @@
 
 ## Reason
 
-It is an extremely dangerous practice to store ROWIDs in a table, except for some very limited scenarios of runtime duration. Any manually explicit or system generated implicit table reorganization will reassign the row's ROWID and break the data consistency.
+It is an extremely dangerous practice to store `rowid`'s in a table, except for some very limited scenarios of runtime duration. Any manually explicit or system generated implicit table reorganization will reassign the row's `rowid` and break the data consistency.
 
-Instead of using ROWID for later reference to the original row one should use the primary key column(s).
+Instead of using `rowid` for later reference to the original row one should use the primary key column(s).
 
 ## Example (bad)
 

docs/4-language-usage/2-variables-and-types/1-general/g-2110.md

@@ -5,7 +5,7 @@
 
 ## Reason
 
-Changing the size of the database column last_name in the employees table from `VARCHAR2(20)` to `VARCHAR2(30)` will result in an error within your code whenever a value larger than the hard coded size is read from the table. This can be avoided using anchored declarations.
+Changing the size of the database column last_name in the employees table from `varchar2(20)` to `varchar2(30)` will result in an error within your code whenever a value larger than the hard coded size is read from the table. This can be avoided using anchored declarations.
 
 ## Example (bad)
 

docs/4-language-usage/2-variables-and-types/1-general/g-2130.md

@@ -14,7 +14,7 @@ Your code will be easier to read as the usage of a variable/constant may be deri
 Type               | Usage
 ------------------ | -----
 `ora_name_type`    | Object corresponding to the ORACLE naming conventions (table, variable, column, package, etc.).
-max_vc2_type       | String variable with maximal VARCHAR2 size.
+`max_vc2_type`     | String variable with maximal VARCHAR2 size.
 `array_index_type` | Best fitting data type for array navigation.
 `id_type`          | Data type used for all primary key (id) columns.
 

docs/4-language-usage/2-variables-and-types/1-general/g-2140.md

@@ -5,7 +5,7 @@
 
 ## Reason
 
-Variables are initialized to NULL by default.
+Variables are initialized to `null` by default.
 
 ## Example (bad)
 

docs/4-language-usage/2-variables-and-types/1-general/g-2150.md

@@ -5,7 +5,7 @@
 
 ## Reason
 
-The NULL value can cause confusion both from the standpoint of code review and code execution. You must always use the `IS NULL` or `IS NOT NULL` syntax when you need to check if a value is or is not `NULL`.
+The `null` value can cause confusion both from the standpoint of code review and code execution. You must always use the `is null` or `is not null` syntax when you need to check if a value is or is not `null`.
 
 ## Example (bad)
 

docs/4-language-usage/2-variables-and-types/1-general/g-2190.md

@@ -5,9 +5,9 @@
 
 ## Reason
 
-Be careful about your use of Oracle-specific data types like `ROWID` and `UROWID`. They might offer a slight improvement in performance over other means of identifying a single row (primary key or unique index value), but that is by no means guaranteed. 
+Be careful about your use of Oracle-specific data types like `rowid` and `urowid`. They might offer a slight improvement in performance over other means of identifying a single row (primary key or unique index value), but that is by no means guaranteed. 
 
-Use of `ROWID` or `UROWID` means that your SQL statement will not be portable to other SQL databases. Many developers are also not familiar with these data types, which can make the code harder to maintain. 
+Use of `rowid` or `urowid` means that your SQL statement will not be portable to other SQL databases. Many developers are also not familiar with these data types, which can make the code harder to maintain. 
 
 ## Example (bad)
 

docs/4-language-usage/2-variables-and-types/2-numeric-data-types/g-2210.md

@@ -5,7 +5,7 @@
 
 ## Reason
 
-If you do not specify precision `NUMBER` is defaulted to 38 or the maximum supported by your system, whichever is less. You may well need all this precision, but if you know you do not, you should specify whatever matches your needs.
+If you do not specify precision `number` is defaulted to 38 or the maximum supported by your system, whichever is less. You may well need all this precision, but if you know you do not, you should specify whatever matches your needs.
 
 ## Example (bad)