diff --git a/guide/03-the-gis/cloning-content.ipynb b/guide/03-the-gis/cloning-content.ipynb
index a991bb593f..0de6ea93ea 100644
--- a/guide/03-the-gis/cloning-content.ipynb
+++ b/guide/03-the-gis/cloning-content.ipynb
@@ -40,7 +40,7 @@
    "source": [
     "One request the Python API team has heard repeatedly from Web GIS administrators: What's the best way to move my content from a development Enterprise or organization to staging to production?\n",
     "\n",
-    "This Guide provides one possible roadmap for how to get content from one Web GIS to another - a template for demonstrating basic software concepts when transferring content so the workflow can be modified for other types of content and tailored for an administrator's particular need. So, first question to answer is: What does it mean to `clone`? Merriam-Webster defines [`clone`](https://www.merriam-webster.com/dictionary/cloning) as the action of _\"propagat[ing] a clone from.\"_ (Didn't I hear my 2nd grade teacher - and every teacher after that for that matter - say it's unhelpful to use the word you are defining in its definition?...) Diving further into the definition of a _\"clone\"_, it reads _\"the aggregate of genetically identical cells or organisms asexually produced by or from a single progenitor cell or orgasm.\"_ Okay, not exactly the context we're working in when discussing a Web GIS. Further along the definition we get to something more along the lines of what we're thinking: _\"one that appears to be a copy of an original form.\"_ BINGO! \n",
+    "This Guide provides one possible roadmap for how to get content from one Web GIS to another - a template for demonstrating basic software concepts when transferring content so the workflow can be modified for other types of content and tailored for an administrator's particular need. So, first question to answer is: What does it mean to `clone`? Merriam-Webster defines [`clone`](https://www.merriam-webster.com/dictionary/cloning) as the action of _\"propagat[ing] a clone from.\"_ (Didn't I hear my 2nd grade teacher - and every teacher after that for that matter - say it's unhelpful to use the word you are defining in its definition?...) Diving further into the definition of a _\"clone\"_, it reads _\"the aggregate of genetically identical cells or organisms asexually produced by or from a single progenitor cell or organism.\"_ Okay, not exactly the context we're working in when discussing a Web GIS. Further along the definition we get to something more along the lines of what we're thinking: _\"one that appears to be a copy of an original form.\"_ BINGO! \n",
     "\n",
     "Leveraging the Python API to clone content from one Web GIS to another can be thought of as _\"propagating content that appears to be a copy of the original content.\"_. Given all the different content and item types, possible Enterprise configurations, potential ArcGIS Online Organization arrangements, security considerations, and item dependencies the [`clone_items()`]((https://developers.arcgis.com/python/api-reference/arcgis.gis.toc.html#arcgis.gis.ContentManager.clone_items)) function aims to _propagate_ an exact duplicate of one item with all its uses and functionality from an original portal to a second portal, but there may be circumstances that lead the clone to come close but not quite produce an identical copy. In addition, the variety of means for publishing items creates varying possibilities for supported, related, or source items created during the publishing process. The relationship between any supported, related, or source items must be considered when cloning an item. For example, the overwrite functionality will not be available on cloned hosted feature layer items, because they do not have a source document from which they were published. The FAQ [here](https://doc.arcgis.com/en/arcgis-online/reference/faq.htm#DELETE_SRC) provides important information regarding source items in ArcGIS Online. However, given our education on `cloning`, we now know that cloning an item produces a second item which appears - but may not be identical to the original. It's important to temper expectations when thinking about the Python API `clone_items()` function. There may be times items will not migrate as expected. \n",
     "\n",
@@ -2096,7 +2096,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "Let's again query the _source_/_target_ dictionary we created when cloning the _source_ web maps to see if we've previously cloned the webmap consumed by the Story Map application."
+    "Let's again query the _source_ \\\\ _target_ dictionary we created when cloning the _source_ web maps to see if we've previously cloned the webmap consumed by the Story Map application."
    ]
   },
   {