diff --git a/examples/ajax/deep.html b/examples/ajax/deep.html
index 2934cf33..b5cc7160 100644
--- a/examples/ajax/deep.html
+++ b/examples/ajax/deep.html
@@ -17,11 +17,11 @@
 					"bProcessing": true,
 					"sAjaxSource": "sources/deep.txt",
 					"aoColumns": [
-						{ "mDataProp": "engine" },
-						{ "mDataProp": "browser" },
-						{ "mDataProp": "platform.inner" },
-						{ "mDataProp": "platform.details.0" },
-						{ "mDataProp": "platform.details.1" }
+						{ "mData": "engine" },
+						{ "mData": "browser" },
+						{ "mData": "platform.inner" },
+						{ "mData": "platform.details.0" },
+						{ "mData": "platform.details.1" }
 					]
 				} );
 			} );
@@ -71,11 +71,11 @@
 		"bProcessing": true,
 		"sAjaxSource": "sources/deep.txt",
 		"aoColumns": [
-			{ "mDataProp": "engine" },
-			{ "mDataProp": "browser" },
-			{ "mDataProp": "platform.inner" },
-			{ "mDataProp": "platform.details.0" },
-			{ "mDataProp": "platform.details.1" }
+			{ "mData": "engine" },
+			{ "mData": "browser" },
+			{ "mData": "platform.inner" },
+			{ "mData": "platform.details.0" },
+			{ "mData": "platform.details.1" }
 		]
 	} );
 } );</pre>
diff --git a/examples/ajax/null_data_source.html b/examples/ajax/null_data_source.html
index 237f8ffb..55345a99 100644
--- a/examples/ajax/null_data_source.html
+++ b/examples/ajax/null_data_source.html
@@ -22,7 +22,7 @@
 						null,
 						null,
 						null,
-						{ "mDataProp": null }
+						{ "mData": null }
 					]
 				} );
 			} );
@@ -35,7 +35,7 @@
 			</div>
 			
 			<h1>Preamble</h1>
-			<p>In some tables it can be useful to not need to specify any data source for a column, as it's content is automatically generated (for example using fnRender). This is fairly common with add, edit and delete columns for a CRUD interface. You can now use the <b>mDataProp</b> set to <i>null</i> to specify that the column has no data source. DataTables will render this column as empty.</p>
+			<p>In some tables it can be useful to not need to specify any data source for a column, as it's content is automatically generated (for example using fnRender). This is fairly common with add, edit and delete columns for a CRUD interface. You can now use the <b>mData</b> set to <i>null</i> to specify that the column has no data source. DataTables will render this column as empty.</p>
 			
 			<h1>Live example</h1>
 			<div id="dynamic">
@@ -67,7 +67,7 @@
 			null,
 			null,
 			null,
-			{ "mDataProp": null }
+			{ "mData": null }
 		]
 	} );
 } );</pre>
diff --git a/examples/ajax/objects.html b/examples/ajax/objects.html
index 27aab16b..f0678dc3 100644
--- a/examples/ajax/objects.html
+++ b/examples/ajax/objects.html
@@ -17,11 +17,11 @@
 					"bProcessing": true,
 					"sAjaxSource": "sources/objects.txt",
 					"aoColumns": [
-						{ "mDataProp": "engine" },
-						{ "mDataProp": "browser" },
-						{ "mDataProp": "platform" },
-						{ "mDataProp": "version" },
-						{ "mDataProp": "grade" }
+						{ "mData": "engine" },
+						{ "mData": "browser" },
+						{ "mData": "platform" },
+						{ "mData": "version" },
+						{ "mData": "grade" }
 					]
 				} );
 			} );
@@ -71,11 +71,11 @@
 		"bProcessing": true,
 		"sAjaxSource": "sources/objects.txt",
 		"aoColumns": [
-			{ "mDataProp": "engine" },
-			{ "mDataProp": "browser" },
-			{ "mDataProp": "platform" },
-			{ "mDataProp": "version" },
-			{ "mDataProp": "grade" }
+			{ "mData": "engine" },
+			{ "mData": "browser" },
+			{ "mData": "platform" },
+			{ "mData": "version" },
+			{ "mData": "grade" }
 		]
 	} );
 } );</pre>
diff --git a/examples/ajax/objects_subarrays.html b/examples/ajax/objects_subarrays.html
index 6b6f90c9..e7ddac09 100644
--- a/examples/ajax/objects_subarrays.html
+++ b/examples/ajax/objects_subarrays.html
@@ -17,11 +17,11 @@
 					"bProcessing": true,
 					"sAjaxSource": "sources/objects_subarrays.txt",
 					"aoColumns": [
-						{ "mDataProp": "engine" },
-						{ "mDataProp": "browser" },
-						{ "mDataProp": "platform" },
-						{ "mDataProp": "details.0" },
-						{ "mDataProp": "details.1" }
+						{ "mData": "engine" },
+						{ "mData": "browser" },
+						{ "mData": "platform" },
+						{ "mData": "details.0" },
+						{ "mData": "details.1" }
 					]
 				} );
 			} );
@@ -71,11 +71,11 @@
 		"bProcessing": true,
 		"sAjaxSource": "sources/objects_subarrays.txt",
 		"aoColumns": [
-			{ "mDataProp": "engine" },
-			{ "mDataProp": "browser" },
-			{ "mDataProp": "platform" },
-			{ "mDataProp": "details.0" },
-			{ "mDataProp": "details.1" }
+			{ "mData": "engine" },
+			{ "mData": "browser" },
+			{ "mData": "platform" },
+			{ "mData": "details.0" },
+			{ "mData": "details.1" }
 		]
 	} );
 } );</pre>
diff --git a/examples/examples_support/syntax/js/shCore.js b/examples/examples_support/syntax/js/shCore.js
index a719d2ff..8fae8fdb 100644
--- a/examples/examples_support/syntax/js/shCore.js
+++ b/examples/examples_support/syntax/js/shCore.js
@@ -2534,6 +2534,8 @@ var dtOptions = [
 'fnStateSaveCallback',
 'bDeferRender',
 'mDataProp',
+'mData',
+'mRender',
 'iDeferLoading',
 'bSortCellsTop',
 'sDefaultContent',
@@ -2642,6 +2644,8 @@ var dtLinks = [
 'fnStateSaveCallback',
 'bDeferRender',
 'mDataProp',
+'mData',
+'mRender',
 'iDeferLoading',
 'bSortCellsTop',
 'sDefaultContent',
diff --git a/examples/server_side/object_data.html b/examples/server_side/object_data.html
index 1258cb76..2fe8152c 100644
--- a/examples/server_side/object_data.html
+++ b/examples/server_side/object_data.html
@@ -18,11 +18,11 @@
 					"bServerSide": true,
 					"sAjaxSource": "scripts/objects.php",
 					"aoColumns": [
-						{ "mDataProp": "engine" },
-						{ "mDataProp": "browser" },
-						{ "mDataProp": "platform" },
-						{ "mDataProp": "version" },
-						{ "mDataProp": "grade" }
+						{ "mData": "engine" },
+						{ "mData": "browser" },
+						{ "mData": "platform" },
+						{ "mData": "version" },
+						{ "mData": "grade" }
 					]
 				} );
 			} );
@@ -36,7 +36,7 @@
 			
 			<h1>Preamble</h1>
 			<p>The "native" data format that DataTables expects for server-side processing is a 2D array of data (rows by columns). However, this is often not flexible enough for either the server-side environment, or you might want to convey more information in the data source than is necessary to show in the table (row IDs from the database for example). For this DataTables supports the reading of data for objects as well as arrays.</p>
-			<p>In this example the server responds with an array of objects, and DataTables will look up each property that is specified by the <b>mDataProp</b> property given for each column</p>
+			<p>In this example the server responds with an array of objects, and DataTables will look up each property that is specified by the <b>mData</b> property given for each column</p>
 			
 			<h1>Live example</h1>
 			<div id="dynamic">
@@ -76,11 +76,11 @@
 		"bServerSide": true,
 		"sAjaxSource": "scripts/objects.php",
 		"aoColumns": [
-			{ "mDataProp": "engine" },
-			{ "mDataProp": "browser" },
-			{ "mDataProp": "platform" },
-			{ "mDataProp": "version" },
-			{ "mDataProp": "grade" }
+			{ "mData": "engine" },
+			{ "mData": "browser" },
+			{ "mData": "platform" },
+			{ "mData": "version" },
+			{ "mData": "grade" }
 		]
 	} );
 } );</pre>