CSS help formatting and info

content/user/template/stylesheet.md

@@ -10,34 +10,33 @@ In Zen Cart, stylesheets are located in this folder:
 
 The CSS files are sent to the browser in this order: (and alphabetically within each case of more than one match):
 
-```
-style*.css // are always loaded and at least ONE should contain site-wide properties. 
+1. `style*.css` // are always loaded and at least ONE should contain site-wide properties. 
 
-language_stylesheet.css // changes to ALL pages, when that language is used
+1. `language_stylesheet.css` // changes to ALL pages, when that language is used
 
-page_name.css // changes to one page (use index_home.css for "just the home page") 
+1. `page_name.css` // changes to one page (use index_home.css for "just the home page") 
 
-pageXXX.css // changes for a specific numbered EZ-Page, ie: page3.css for ez-page id=3 
+1. `pageXXX.css` // changes for a specific numbered EZ-Page, ie: page3.css for ez-page id=3 
 
-language_page_name.css // changes to one page, when that language is used
+1. `language_page_name.css` // changes to one page, when that language is used
 
-c_??.css // changes to all info pages in a category
+1. `c_??.css` // changes to all info pages in a category
 
-language_c_??.css // changes to all info pages in a category, when that language is used
+1. `language_c_??.css` // changes to all info pages in a category, when that language is used
 
-c_??_??_children.css // changes for all children of the specified parent. Also supports a language prefix. 
+1. `c_??_??_children.css` // changes for all children of the specified parent. Also supports a language prefix. 
 
-m_??.css // changes to a manufacturer's listing page
+1. `m_??.css` // changes to a manufacturer's listing page
 
-language_m_??.css // changes to a manufacturer's listing page, when that language is used
+1. `language_m_??.css` // changes to a manufacturer's listing page, when that language is used
 
-p_??.css // changes to a product's info page
+1. `p_??.css` // changes to a product's info page
 
-language_p_??.css // changes to a product's info page, when that language is used
+1. `language_p_??.css` // changes to a product's info page, when that language is used
 
-print*.css // printer-friendly global usage site-wide changes for printing-only 
-```
-The stylesheet.css always loads first and should contain the bulk of your CSS selectors. Each file loaded takes priority over previously loaded file(s). To save loading time, only new selectors or selectors whose properties you wish to change should be in the subsequent optional CSS files. You can have different overrides for the same page, in different languages, because the two would never be called at the same time.
+1. `print*.css` // printer-friendly global usage site-wide changes for printing-only 
+
+The `stylesheet.css` always loads first and should contain the bulk of your CSS selectors. Each file loaded takes priority over previously loaded file(s). To save loading time, only new selectors or selectors whose properties you wish to change should be in the subsequent optional CSS files. You can have different overrides for the same page, in different languages, because the two would never be called at the same time.
 
 `If someone selected the French language on your site, the `french_stylesheet.css` would also be loaded. It should only contain the site-wide changes you want to make to `stylesheet.css`. 
 
@@ -51,9 +50,11 @@ Possibly you created a NEW tag for your Privacy Statement. It is defined in only
 
 Because, in Germany, that phrase must be in all CAPS, but not in other countries.
 
-Use your CSS files and the standard tags as much as possible; just change their properties when needed. If possible, DON'T HACK the core code. Use your CSS files to do the work for you.
+Use your CSS files and the standard tags as much as possible; just change their properties when needed. If possible, DON'T MODIFY the core code. Use your CSS files to do the work for you.
 
 If you refrain from altering the core files, then you will find that upgrades and maintenance are much easier.
 
-
+Helpful tips testing CSS changes: 
+- Watch out for [browser caching](/user/new_user_topics/browser_caching/).
+- Use [Inspect in Google Chrome](/user/running/inspect/).