diff --git a/README.txt b/README.txt
index e027040..3f1dee3 100644
--- a/README.txt
+++ b/README.txt
@@ -13,11 +13,11 @@ field collection item may also be viewed and edited separately.
  ------
 
   * Add a field collection field to any entity, e.g. to a node. For that use the
-   the usual "Manage fields" interface provided by the "field ui" module of
-   Drupal, e.g. "Admin -> Structure-> Content types -> Article -> Manage fields".
+    the usual "Manage fields" interface provided by the "field ui" module.
+    e.g. "Admin -> Structure-> Content types -> Article -> Manage fields".
 
   * Then go to "Admin -> Structure-> Field collection" to define some fields for
-   the created field collection.
+    the created field collection.
 
   * By the default, the field collection is not shown during editing of the host
     entity. However, some links for adding, editing or deleting field collection
@@ -28,9 +28,20 @@ field collection item may also be viewed and edited separately.
     module might provide such widgets itself too.
 
 
-Restrictions
--------------
+ Using field collection with entity translation
+ -----------------------------------------------
 
-  * As of now, the field collection field does not properly respect field
-    translation. Thus, for now it is suggested to only use the field for
-    entities that are not translatable.
+  * Field collection items must be selected as a translatable entity type at
+    Admin -> Config -> Regional -> Entity Translation.
+
+  * The common use case is to leave the field collection field untranslatable
+    and set the necessary fields inside it to translatable.  There is currently
+    a known issue where a host can not be translated unless it has at least
+    one other field that is translatable, even if some fields inside one of
+    its field collections are translatable.
+
+  * The alternate use case is to make the field collection field in the host
+    translatable.  If this is done it does not matter whether the inner fields
+    are set to translatable or not, they will all be translatable as every
+    language for the host will have a completely separate copy of the field
+    collection item(s).