From 5e5f6eb6e3a94aeb22bc09f3e4ad3211dbe84690 Mon Sep 17 00:00:00 2001 From: dweezil Date: Fri, 24 Nov 2017 15:09:23 -0500 Subject: [PATCH] fix typo --- _includes/sqlstyle.guide.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_includes/sqlstyle.guide.md b/_includes/sqlstyle.guide.md index 5a184f0..0ae7dae 100644 --- a/_includes/sqlstyle.guide.md +++ b/_includes/sqlstyle.guide.md @@ -273,7 +273,7 @@ SELECT r.last_name Subqueries should also be aligned to the right side of the river and then laid out using the same style as any other query. Sometimes it will make sense to have -the closing parenthesis on a new line at the same character position as it's +the closing parenthesis on a new line at the same character position as its opening partner—this is especially true where you have nested subqueries. ```sql @@ -343,7 +343,7 @@ about though so it is important that a standard set of guidelines are followed. #### Choosing keys -Deciding the column(s) that will form the keys in the definition should be a +Deciding the column(s) that will form the keys in the definition should be a carefully considered activity as it will effect performance and data integrity. 1. The key should be unique to some degree. @@ -1276,7 +1276,7 @@ ZONE [rivers]: http://practicaltypography.com/one-space-between-sentences.html "Practical Typography: one space between sentences" [reserved-keywords]: #reserved-keyword-reference - "Reserved keyword reference" + "Reserved keyword reference" [eav]: https://en.wikipedia.org/wiki/Entity%E2%80%93attribute%E2%80%93value_model "Wikipedia: Entity–attribute–value model" [sqlstyleguide]: http://www.sqlstyle.guide