Merge pull request #458 from vatpac-technology/banner

Update Banner Image

Author: alphadelta332

docs/aerodromes/classc/img/MLTCUairspace.png

@@ -44,18 +44,18 @@ Describe any altitudes in the format of `Axxx` (for altitudes below 10,000ft) or
 It is recommended to include an example highlighting any unique or lesser-known radio calls which apply to a procedure, and to indicate any coordination requirements associated with a position.  
 
 ### Radio Calls
-Radio calls should take the following format:  
+Radio calls should be wrapped in a **Phraseology** admonition and take the following format:  
 
 ``` md
 **STATION NAME**: "Message"
 ```
 
-!!! example
+!!! phraseology
     **VOZ1545**: "VOZ1545, request descent"  
     **HUO**: "VOZ1545, descend to FL130" 
 
 ### Coordination
-Coordination examples should take the following format:  
+Coordination examples should generally be wrapped in a **Phraseology** admonition and take the following format:  
 
 ``` md
 **INITIATING SECTOR** -> **RECEIVING SECTOR**: "Message"
@@ -73,7 +73,7 @@ As a general rule of thumb, hotlines should be used in all circumstances, except
 - Oceanic coordination  
 - Airways clearance requests from ACD to overlying TCU/ENR position (e.g. Sydney Delivery requesting clearance to YSBK on behalf of an aircraft)
 
-!!! example
+!!! phraseology
     <span class="coldline">**NW TCU** -> **WOL**</span>: "Taxi, PSDN18 for YMCO via URBOB, Requesting F130"  
     <span class="coldline">**WOL** -> **NW TCU**</span>: "PSDN18, F130"  
     <span class="coldline">**NW TCU** -> **WOL**</span>: "F130, PSDN18" 

docs/aerodromes/classc/img/victor_routes.png

@@ -40,6 +40,9 @@ Images also use the default markdown syntax, but can have some additional proper
 
 You can also add multiple properties together, with a space between the attributes.
 
+!!! warning "Important"
+    All images should be optimised for the web. This can be done easily using a service like [tinify](https://tinypng.com){ target=new }.
+
 #### Image Captions
 
 Where confusion can arise from the placement or relevance of an image, you can opt to use a caption. Unfortunately these are not natively supported by Markdown, but you can opt to use HTML.
@@ -65,5 +68,10 @@ Admonitions are enabled and are very handy for delivering extra information that
 
 You can see a list of [all admonition blocks here](https://squidfunk.github.io/mkdocs-material/reference/admonitions/){target=new}.
 
+!!! warning "Important"
+    To fit the styling of the site, do not use the default `!!! important` admonition. All **Important** blocks should be formatted as a *Warning* block, with a custom title.
+
+    `!!! warning "Important"`
+
 !!! note
     Never use collapsible blocks - if it needs the additional information drawn to it, it should be displayed all the time.