diff --git a/src/main/asciidoc/index.adoc b/src/main/asciidoc/index.adoc
index 06af851c7..982ce1f68 100644
--- a/src/main/asciidoc/index.adoc
+++ b/src/main/asciidoc/index.adoc
@@ -5,7 +5,7 @@ Michael Hunger; Oliver Gierke; Vince Bickers; Adam George; Luanne Misquitta; Mic
 :revnumber: {version}
 :revdate: {localdate}
 
-Spring Data Neo4j Version 4 (September 2015)
+Spring Data Neo4j Version 4.1 (October 2015)
 
 (C) 2010-2015 Graph Aware Ltd - Neo Technology, Inc. - Pivotal Software, Inc.
 
diff --git a/src/main/asciidoc/reference/migration/migration.adoc b/src/main/asciidoc/reference/migration/migration.adoc
index 5e6ca85d5..fedf1757e 100644
--- a/src/main/asciidoc/reference/migration/migration.adoc
+++ b/src/main/asciidoc/reference/migration/migration.adoc
@@ -34,6 +34,13 @@ SDN 4 provides automatic type conversion for the obvious candidates: byte[] and
 BigInteger types. In order to define bespoke type conversions for particular entity attribute, you can annotate a
 field or method with `@Convert` to specify your own implementation of `org.neo4j.ogm.typeconversion.AttributeConverter`.
 
+
+[NOTE]
+====
+The default Date converter is <<reference_programming-model_conversion-built_in,@DateString>>.
+Use the `@DateLong` annotation when migrating from previous versions of SDN which represented Dates as Long.
+====
+
 You can find out more about type conversions here: <<reference_programming-model_conversion-custom,Custom Converters>>
 
 == Obsolete Annotations
diff --git a/src/main/asciidoc/reference/programming-model/attachdetach.adoc b/src/main/asciidoc/reference/programming-model/attachdetach.adoc
index 8e69fd7a4..fc5ab94ae 100644
--- a/src/main/asciidoc/reference/programming-model/attachdetach.adoc
+++ b/src/main/asciidoc/reference/programming-model/attachdetach.adoc
@@ -113,7 +113,7 @@ Behind the scenes however, repository-based paging and sorting delegates to the
 
 [NOTE]
 ====
-Spring Data Neo4j 4 does not yet support sorting and paging on derived query methods.
+Spring Data Neo4j 4 does not yet support sorting and paging on custom queries or derived query methods.
 ====
 
 ====
diff --git a/src/main/asciidoc/reference/programming-model/relationships.adoc b/src/main/asciidoc/reference/programming-model/relationships.adoc
index 8dfc33344..597638d88 100644
--- a/src/main/asciidoc/reference/programming-model/relationships.adoc
+++ b/src/main/asciidoc/reference/programming-model/relationships.adoc
@@ -112,6 +112,7 @@ Note that the `Actor` also contains a reference to a `Role`.  This is important
 Therefore, you need to structure your domain models so that relationship entities are reachable from node entities for this to work correctly.
 
 Additionally, SDN4 will not persist a relationship entity that doesn't have any properties defined.  If you don't want to include properties in your relationship entity then you should use a plain `@Relationship` instead.
+Multiple relationship entities which have the same property values and relate the same nodes are indistinguishable from each other and are represented as a single relationship by SDN 4.
 
 In previous versions of Spring Data Neo4j, a dynamic relationship type field was supported.  
 However, this has been dropped completely for version 4, since it was not possible to manage it effectively for both reading from and writing to the graph.
diff --git a/src/main/asciidoc/reference/programming-model/repositories.adoc b/src/main/asciidoc/reference/programming-model/repositories.adoc
index 3939daf2d..1c2b9e91b 100644
--- a/src/main/asciidoc/reference/programming-model/repositories.adoc
+++ b/src/main/asciidoc/reference/programming-model/repositories.adoc
@@ -140,7 +140,7 @@ public interface PersonRepository extends GraphRepository<Person> {
 
 [NOTE]
 ====
-In the current version, derived finders do not support paging, sorting or a custom depth.
+In the current version, derived finders and custom queries do not support paging, sorting or a custom depth.
 ====
 
 
diff --git a/src/main/asciidoc/reference/programming-model/template.adoc b/src/main/asciidoc/reference/programming-model/template.adoc
index 12a06a4a5..911c6d2eb 100644
--- a/src/main/asciidoc/reference/programming-model/template.adoc
+++ b/src/main/asciidoc/reference/programming-model/template.adoc
@@ -41,7 +41,9 @@ An `org.neo4j.ogm.session.result.Result` is returned. This consists of `org.neo4
 modifying cypher statements if applicable, and an `Iterable<Map<String,Object>>` containing the raw data, which can be either used as-is or converted into a richer type if needed.
 The keys in each `Map` correspond to the names listed in the return clause of the executed Cypher query.
 
-For the query methods that retrieve mapped objects, the recommended query format is to return a path, which should ensure that known types get mapped correctly and joined together with relationships as appropriate.
+//For the query methods that retrieve mapped objects, the recommended query format is to return a path, which should ensure that known types get mapped correctly and joined together with relationships as appropriate.
+[NOTE]
+Modifications made to the graph via Cypher queries directly will not be reflected in your domain objects within the session.
 
 == Transactions
 
diff --git a/src/main/resources/notice.txt b/src/main/resources/notice.txt
index b1e191a5a..a60cff51d 100644
--- a/src/main/resources/notice.txt
+++ b/src/main/resources/notice.txt
@@ -1,4 +1,4 @@
-Spring Data Neo4j 4.0 RC2
+Spring Data Neo4j 4.1
 Copyright (c) [2011-2015] Pivotal Software, Inc. / Neo Technologies, Inc. / GraphAware Ltd.
 
 This product is licensed to you under the Apache License, Version 2.0 (the "License").