Updating breaking changes

- field names cannot be mapped with `.` in them
- fixed asciidoc issue where the list was not recognized as a list

docs/reference/migration/migrate_2_0.asciidoc

@@ -284,6 +284,27 @@ curl -XGET 'localhost:9200/index/type/_search'
 }
 ---------------
 
+==== Removed support for `.` in field name mappings
+Prior to Elasticsearch 2.0, a field could be defined to have a `.` in its name.
+Mappings like the one below have been deprecated for some time and they will be
+blocked in Elasticsearch 2.0.
+
+[source,js]
+---------------
+curl -XPUT 'localhost:9200/index'
+{
+  "mappings": {
+    "type": {
+      "properties": {
+        "name.first": {
+          "type": "string"
+        }
+      }
+    }
+  }
+}
+---------------
+
 ==== Meta fields have limited configuration
 Meta fields (those beginning with underscore) are fields used by elasticsearch
 to provide special features.  They now have limited configuration options.
@@ -376,6 +397,7 @@ The ability to specify mappings in configuration files has been removed. To spec
 default mappings that apply to multiple indexes, use index templates.
 
 The following settings are no longer valid:
+
 * `index.mapper.default_mapping_location`
 * `index.mapper.default_percolator_mapping_location`