Update style_guide

source/documentation/tools/create-a-derived-table/style_guide

@@ -11,7 +11,7 @@ Style might seem like a trivial, surface-level issue, but it's an important aspe
 
 As a group of Analytics Engineers, we have thoroughly reviewed guidance published by dbt (the technology behind create-a-derived-table) and adapted it to suit our needs in this style guide.
 
-Please take the time to familiarise yourself with this style guide, and our guidance on project structure [add link], before starting projects in create-a-derived-table.
+Please take the time to familiarise yourself with this style guide before starting projects in create-a-derived-table.
 
 ## What's important about style?
 
@@ -29,8 +29,8 @@ Once you've established a clear style, stay consistent. This is the most importa
 ## Fields and model names
 
 ### Essential styling
-- 🔑 Each model should have a primary key and that primary key should be the first field in the table.
-- 🔑 The primary key of a model should be named `<object>_id`, for example, `account_id`. This makes it easier to know what `id` is being referenced in downstream joined models.
+-🔑 Each model should have a primary key and that primary key should be the first field in the table.
+-🔑 The primary key of a model should be named `<object>_id`, for example, `account_id`. This makes it easier to know what `id` is being referenced in downstream joined models.
 - Use underscores for naming dbt models; avoid dots or camel case.
   - ✅ `models_without_dots`
   - ❌ `models.with.dots`