diff --git a/guide/02-api-overview/overview24.ipynb b/guide/02-api-overview/overview24.ipynb
index e9cf13e59..649a7538c 100644
--- a/guide/02-api-overview/overview24.ipynb
+++ b/guide/02-api-overview/overview24.ipynb
@@ -249,7 +249,7 @@
    "source": [
     "The previous `arcgis.widgets` module contained the [MapView](/python-2-3/api-reference/arcgis.widgets.html#mapview) class which served as the map widget in Jupyter notebooks. The Python API 2.4 release refactors the _MapView_ functionality into two new classes in the [`arcgis.map`](/python/latest/api-reference/arcgis.map.toc.html) module: [_Map_](/python/latest/api-reference/arcgis.map.toc.html#map) and [_Scene_](/api-reference/arcgis.map.toc.html#scene) classes.\n",
     "\n",
-    "In previous releases, maps and scenes were intialized based on the _mode_ argument entered in the [GIS.map()](/python/latest/api-reference/arcgis.gis.toc.html#arcgis.gis.GIS.map) method, or by setting the [_mode_](/python-2-3/api-reference/arcgis.widgets.html#arcgis.widgets.MapView.mode) property of a _MapView_ object.  Either way, you were always working with an instance of the _MapView_ class. You can still use the _mode_ argument when intializing the _gis.map()_ object, but rather than returning the same type of object, the default value of _2D_ will return a _Map_ object, and _3D_ will return a _Scene_ object. Refactoring the calls allowed Python development to align with the [web map specification](https://developers.arcgis.com/web-map-specification/) and the [web scene specification](https://developers.arcgis.com/web-map-specification/) directly. This will increase widget compatibility within notebooks to more closely reflect the browser experiences of the Map Viewer and Scene Viewer.\n",
+    "In previous releases, maps and scenes were intialized based on the _mode_ argument entered in the [GIS.map()](/python/latest/api-reference/arcgis.gis.toc.html#arcgis.gis.GIS.map) method, or by setting the [_mode_](/python-2-3/api-reference/arcgis.widgets.html#arcgis.widgets.MapView.mode) property of a _MapView_ object.  Either way, you were always working with an instance of the _MapView_ class. You can still use the _mode_ argument when intializing the _gis.map()_ object, but rather than returning the same type of object, the default value of _2D_ will return a _Map_ object, and _3D_ will return a _Scene_ object. Refactoring the calls allowed Python development to align with the [web map specification](https://developers.arcgis.com/web-map-specification/) and the [web scene specification](https://developers.arcgis.com/web-scene-specification/) directly. This will increase widget compatibility within notebooks to more closely reflect the browser experiences of the Map Viewer and Scene Viewer.\n",
     "\n",
     "Some properties and methods on the _MapView_ class have been entirely removed, including interactive functionality that could be programmed into specific events like _on_click_ and _on_draw_, embedding the widget into the notebook, and properties and methods that controlled the Jupyter environment. Other properties and methods have been refactored into new classes, many using the exact same name. See the table below for a mapping between previous _MapView_ method and property names and how to access that functionality within the 2.4 release.\n",
     "\n",
@@ -492,7 +492,7 @@
    "name": "python",
    "nbconvert_exporter": "python",
    "pygments_lexer": "ipython3",
-   "version": "3.11.10"
+   "version": "3.12.9"
   }
  },
  "nbformat": 4,