typo fixes

Author: nparavicini7

guide/13-managing-arcgis-applications/cloning-complex-apps.ipynb

@@ -17,7 +17,7 @@
     "\n",
     "We're going to look at a few things in this guide:\n",
     "\n",
-    "- New clonable item types in 2.2.0\n",
+    "- New cloneable item types in 2.2.0\n",
     "- How to dive into an item's structure\n",
     "- Strategies for remapping data"
    ]
@@ -38,9 +38,9 @@
     "\n",
     "### 'Complex Items' and `search_existing_items`\n",
     "\n",
-    "What do we mean when we say \"complex items?\" In this context, we're referring to items that may contain other items within them. One of the most important facets of cloning these complex items is making sure that all of their internal items are properly accounted for in the target GIS organisation. That can mean making sure those items are also cloned, replaced with other items that already exist in the new GIS, or come from sources accessible by any GIS (such as Living Atlas items). Regardless of the method, the underlying structure of the newly cloned item must refer to items that can be used in the new GIS. This guide will cover a handful of strategies for cloning item dependencies and confirming they're being incorporated properly.\n",
+    "What do we mean when we say \"complex items?\" In this context, we're referring to items that may contain other items within them. One of the most important facets of cloning these complex items is making sure that all of their internal items are properly accounted for in the target GIS organization. That can mean making sure those items are also cloned, replaced with other items that already exist in the new GIS, or come from sources accessible by any GIS (such as Living Atlas items). Regardless of the method, the underlying structure of the newly cloned item must refer to items that can be used in the new GIS. This guide will cover a handful of strategies for cloning item dependencies and confirming they're being incorporated properly.\n",
     "\n",
-    "One of the most critical tools when cloning these items is the `clone_items()` function's `search_existing_arguments` argument. When this is set to `True` (which it is by default), the function searches to see if all of the items set to be cloned (this includes all items in the `items` argument and their internal data sources) already exist in the target GIS organisation. When an item is cloned, it gets given a specific `typeKeyword` indicating its source item, so the function searches for items with those matching keywords. This means that items with matching names and data types will not get used if they aren't a clone of the item in question. When `search_existing_items` is set to `False`, all items will get cloned (even if clones of them already exist in the target), unless they're not clonable or covered in a dictionary passed in as the `item_mapping` argument (more on this later)."
+    "One of the most critical tools when cloning these items is the `clone_items()` function's `search_existing_items` argument. When this is set to `True` (which it is by default), the function searches to see if all of the items set to be cloned (this includes all items in the `items` argument and their internal data sources) already exist in the target GIS organization. When an item is cloned, it gets given a specific `typeKeyword` indicating its source item, so the function searches for items with those matching keywords. This means that items with matching names and data types will not get used if they aren't a clone of the item in question. When `search_existing_items` is set to `False`, all items will get cloned (even if clones of them already exist in the target), unless they're not cloneable or covered in a dictionary passed in as the `item_mapping` argument (more on this later)."
    ]
   },
   {
@@ -499,7 +499,7 @@
    "source": [
     "## StoryMaps, Web Scenes, and Item Remapping\n",
     "\n",
-    "Version 2.2.0 also smoothes over cloning for another popular item type- [ArcGIS StoryMaps](https://www.esri.com/en-us/arcgis/products/arcgis-storymaps/overview). StoryMaps can contain numerous media types and different types of ArcGIS items, which `clone_items()` should cover- we're going to show how users can examine the items in their StoryMap and confirm that both the StoryMap and all of the internal items were cloned properly.\n",
+    "Version 2.2.0 also smoothes over cloning for another popular item type- [ArcGIS StoryMaps](/python/api-reference/arcgis.apps.storymap.html#storymap). StoryMaps can contain numerous media types and different types of ArcGIS items, which `clone_items()` should cover- we're going to show how users can examine the items in their StoryMap and confirm that both the StoryMap and all of the internal items were cloned properly.\n",
     "\n",
     "We'll start by grabbing a StoryMap using the portal item ID, and then use a couple methods to examine the content within the item: using the ArcGIS API for Python's StoryMap class, and accessing the item's internal JSON structure."
    ]
@@ -551,7 +551,7 @@
    "id": "e803e217",
    "metadata": {},
    "source": [
-    "Using the Python API's `StoryMap` module, we can get a general overview of what's in the StoryMap with the `content_list` property."
+    "Using the Python API's `StoryMap` module, we can get a general overview of what's in the StoryMap with the [content list](/python/api-reference/arcgis.apps.storymap.html#arcgis.apps.storymap.story.StoryMap.content_list) property."
    ]
   },
   {
@@ -694,7 +694,7 @@
    "id": "3f074c4b",
    "metadata": {},
    "source": [
-    "Above you'll see all of the info about what's contained within the StoryMap. All that's in there currently is a Web Scene, which simplifies things; we just know that Web Scene needs to be cloned across. The draft JSON of the cloned StoryMap should match this, except with a select few things adjusted to the new organisation, such as `itemId`.\n",
+    "Above you'll see all of the info about what's contained within the StoryMap. All that's in there currently is a Web Scene, which simplifies things; we just know that Web Scene needs to be cloned across. The draft JSON of the cloned StoryMap should match this, except with a select few things adjusted to the new organization, such as `itemId`.\n",
     "\n",
     "We're going to assign the output of the `clone_items()` call to a variable called `clone_list`. This will be a list of the ArcGIS items that got cloned over."
    ]
@@ -870,7 +870,7 @@
    "id": "d9ab635a",
    "metadata": {},
    "source": [
-    "As we can see, the results are essentially the same, minus one difference: the key of the resource and the `itemId` are different. The Web Scene got cloned over to the new organisation, and our cloned StoryMap properly points to the new one."
+    "As we can see, the results are essentially the same, minus one difference: the key of the resource and the `itemId` are different. The Web Scene got cloned over to the new organization, and our cloned StoryMap properly points to the new one."
    ]
   },
   {
@@ -1097,9 +1097,9 @@
    "id": "40cca7d6",
    "metadata": {},
    "source": [
-    "Using the `itemId` key in there, we can see exactly which item is being used in there. Say we already have an item in the target org we want to replace that particular item with; we would construct an `item_mapping` dictionary with the original item's ID as the key and the target item's ID as the value. This dictionary can be contructed with as many appropriate item ID's as necessary.\n",
+    "Using the `itemId` key in there, we can see exactly which item is being used in there. Say we already have an item in the target organization we want to replace that particular item with; we would construct an `item_mapping` dictionary with the original item's ID as the key and the target item's ID as the value. This dictionary can be contructed with as many appropriate item ID's as necessary.\n",
     "\n",
-    "Let's say we already have another Everest Web Scene in our target organisation that we want to use instead; we would just have to find the item ID of that item, which is '502c4f1454d34766807e1268c09acf34'. If we we were to clone this StoryMap again, we could make our cloned StoryMap use this target item. We just pass in an `item_mapping` dictionary, and set the item ID of the source item we want to replace as the key, and set the item ID of the desired item in the target GIS as the value."
+    "Let's say we already have another Everest Web Scene in our target organization that we want to use instead; we would just have to find the item ID of that item, which is '502c4f1454d34766807e1268c09acf34'. If we we were to clone this StoryMap again, we could make our cloned StoryMap use this target item. We just pass in an `item_mapping` dictionary, and set the item ID of the source item we want to replace as the key, and set the item ID of the desired item in the target GIS as the value."
    ]
   },
   {
@@ -1260,7 +1260,7 @@
     "As you've just seen, accessing an item's data gives you great insight into what's going on. Having direct access to the structure of the item's data also gives you a great tool to troubleshoot when something doesn't quite go right with your cloning. \n",
     "\n",
     "\n",
-    "ArcGIS Dashboards aren't actively supported with their own module in the Python API, but they're still cloneable. There are a couple caveats, such as `item_mapping` not being usable, but using the tricks we've covered in this guide, users can still move them across organisations and remap their data. This makes them the perfect example of how to troubleshoot something by hand using methods found in the `gis.item` module."
+    "ArcGIS Dashboards aren't actively supported with their own module in the Python API, but they're still cloneable. There are a couple caveats, such as `item_mapping` not being usable, but using the tricks we've covered in this guide, users can still move them across organizations and remap their data. This makes them the perfect example of how to troubleshoot something by hand using methods found in the `gis.item` module."
    ]
   },
   {