diff --git a/doc/Tutorials/Dynamic_Map.ipynb b/doc/Tutorials/Dynamic_Map.ipynb
index 046988d090..dda175a158 100644
--- a/doc/Tutorials/Dynamic_Map.ipynb
+++ b/doc/Tutorials/Dynamic_Map.ipynb
@@ -521,7 +521,7 @@
    "outputs": [],
    "source": [
     "hv.DynamicMap(shapes, kdims=[hv.Dimension('N', values=[2,3,4,5]), \n",
-    "                             hv.Dimension('radius', values=[0.7,0.8,0.9,1])])\n"
+    "                             hv.Dimension('radius', values=[0.7,0.8,0.9,1])])"
    ]
   },
   {
@@ -1202,7 +1202,9 @@
    "source": [
     "Here we use ``+axiswise`` to see the behavior of the two cases independently. We see in **A** that when ``vrange=False`` and no range is set on the value dimension, no automatic normalization occurs (as it would for a ``HoloMap``). In **B** we see that normalization is applied but only when the value dimension range has been specified. \n",
     "\n",
-    "In other words ``DynamicMaps`` do not support automatic normalization across their elements but do support the same explicit normalization behavior as ``HoloMaps``. Values that are generated outside this range are simply clipped according the usual semantics of explicit value dimension ranges."
+    "In other words ``DynamicMaps`` do not support automatic normalization across their elements but do support the same explicit normalization behavior as ``HoloMaps``. Values that are generated outside this range are simply clipped according the usual semantics of explicit value dimension ranges. \n",
+    "\n",
+    "Note that we can always have the option of casting a ``DynamicMap`` to a ``HoloMap`` in order to automatically normalize across the cached values without needing explicit value dimension ranges."
    ]
   },
   {