website/docs/best-practices/how-we-style/2-how-we-style-our-sql.md|28 col 40| [custom.LatinAbbreviations] Avoid Latin abbreviations: 'for example'. Consider using 'eg' instead.
website/docs/best-practices/how-we-style/2-how-we-style-our-sql.md|34 col 40| [custom.Typos] Oops there's a typo -- did you really mean 'i.e.'?
website/docs/best-practices/how-we-style/2-how-we-style-our-sql.md|34 col 40| [custom.LatinAbbreviations] Avoid Latin abbreviations: 'that is'. Consider using 'i.e' instead.
website/docs/best-practices/how-we-style/2-how-we-style-our-sql.md|38 col 4| [custom.SentenceCaseHeaders] ''Import' CTEs' should use sentence-style capitalization. Try '' instead.
website/docs/best-practices/how-we-style/2-how-we-style-our-sql.md|63 col 4| [custom.SentenceCaseHeaders] ''Functional' CTEs' should use sentence-style capitalization. Try '' instead.
website/docs/best-practices/how-we-style/2-how-we-style-our-sql.md|66 col 69| [custom.Typos] Oops there's a typo -- did you really mean 'e.g.'?
website/docs/best-practices/how-we-style/2-how-we-style-our-sql.md|66 col 69| [custom.LatinAbbreviations] Avoid Latin abbreviations: 'for example'. Consider using 'e.g' instead.