Changes in 5d6205a: Updated Izenda Vision (markdown)

				Guides/Izenda-Vision.md
			
          @@ -12,7 +12,7 @@ When creating a visualization, you must pay specific attention to the field orde

           **Field Order and Group Hierarchy**

          -Some visualizations permit multiple group fields. Group field hierarchy must be placed in proper field order! This means highest category first, and lowest category last. Here are some examples:

          +Some visualizations permit multiple group fields. Group field hierarchy must be placed in proper field order. This means highest category first, and lowest category last. Here are some examples:

           Country, State/Region, City, Neighborhood

          @@ -20,7 +20,7 @@ Company, Department, Office, Desk

           Tera, Giga, Mega, Kilo

          -Expressions read the exact field order as you define it. If I place Neighborhood before Country, my visualization will not make any sense by definition! Double check that fields are in the correct order if the visualization does not appear to be correct.

          +Expressions read the exact field order as you define it. If I place Neighborhood before Country, my visualization will not make any sense by definition. Double check that fields are in the correct order if the visualization does not appear to be correct.

           **Field Sorting**

          @@ -48,10 +48,10 @@ Some visualizations do not care where a field is, so long as it exists. These fi

           These terms refer to the types of columns that each visualization reads.

          -**Group** - This column can be any data type, aggregated or not aggregated. These columns are used to group data in other columns, and often serve as the axis or scale of a particular visualization.  

          -**Time** - This column must be a Datetime data type.  

          -**Metric** - This column can be any data type. It is generally an aggregate, and most commonly a numeric, but does not have to be. These columns are the elements that are being charted, mapped, or displayed on your visualization. 

          -**Geographic Field** - This column is a special case. It is used in map-style visualizations. It must be a list of geographic entities, such as a list of countries, regions, or states.

          +* **Group** - This column can be any data type, aggregated or not aggregated. These columns are used to group data in other columns, and often serve as the axis or scale of a particular visualization.  

          +* **Time** - This column must be a Datetime data type.  

          +* **Metric** - This column can be any data type. It is generally an aggregate, and most commonly a numeric, but does not have to be. These columns are the elements that are being charted, mapped, or displayed on your visualization. 

          +* **Geographic Field** - This column is a special case. It is used in map-style visualizations. It must be a list of geographic entities, such as a list of countries, regions, or states.

           #Visualization Styles:

...	...	@@ -12,7 +12,7 @@ When creating a visualization, you must pay specific attention to the field orde
12	12
13	13	Field Order and Group Hierarchy
14	14
15		-Some visualizations permit multiple group fields. Group field hierarchy must be placed in proper field order! This means highest category first, and lowest category last. Here are some examples:
	15	+Some visualizations permit multiple group fields. Group field hierarchy must be placed in proper field order. This means highest category first, and lowest category last. Here are some examples:
16	16
17	17	Country, State/Region, City, Neighborhood
18	18
...	...	@@ -20,7 +20,7 @@ Company, Department, Office, Desk
20	20
21	21	Tera, Giga, Mega, Kilo
22	22
23		-Expressions read the exact field order as you define it. If I place Neighborhood before Country, my visualization will not make any sense by definition! Double check that fields are in the correct order if the visualization does not appear to be correct.
	23	+Expressions read the exact field order as you define it. If I place Neighborhood before Country, my visualization will not make any sense by definition. Double check that fields are in the correct order if the visualization does not appear to be correct.
24	24
25	25	Field Sorting
26	26
...	...	@@ -48,10 +48,10 @@ Some visualizations do not care where a field is, so long as it exists. These fi
48	48
49	49	These terms refer to the types of columns that each visualization reads.
50	50
51		-Group - This column can be any data type, aggregated or not aggregated. These columns are used to group data in other columns, and often serve as the axis or scale of a particular visualization.
52		-Time - This column must be a Datetime data type.
53		-Metric - This column can be any data type. It is generally an aggregate, and most commonly a numeric, but does not have to be. These columns are the elements that are being charted, mapped, or displayed on your visualization.
54		-Geographic Field - This column is a special case. It is used in map-style visualizations. It must be a list of geographic entities, such as a list of countries, regions, or states.
	51	+* Group - This column can be any data type, aggregated or not aggregated. These columns are used to group data in other columns, and often serve as the axis or scale of a particular visualization.
	52	+* Time - This column must be a Datetime data type.
	53	+* Metric - This column can be any data type. It is generally an aggregate, and most commonly a numeric, but does not have to be. These columns are the elements that are being charted, mapped, or displayed on your visualization.
	54	+* Geographic Field - This column is a special case. It is used in map-style visualizations. It must be a list of geographic entities, such as a list of countries, regions, or states.
55	55
56	56	#Visualization Styles:
57	57