diff --git a/samples/augment-reality-to-show-tabletop-scene/README.md b/samples/augment-reality-to-show-tabletop-scene/README.md
index 20ab46fb5..580a9d4b9 100644
--- a/samples/augment-reality-to-show-tabletop-scene/README.md
+++ b/samples/augment-reality-to-show-tabletop-scene/README.md
@@ -16,7 +16,7 @@ NOTE: [Google Play Services for AR](https://play.google.com/store/apps/details?i
 
 ## How it works
 
-1. Create a `TableTopSceneView` with `anchorPoint`, `translationFactor`, `clippingDistance`, and a `scene`.
+1. Create a `TableTopSceneView` with `arcGISSceneAnchor`, `translationFactor`, `clippingDistance`, and an `arcGISScene`.
 2. For this sample, the `anchorPoint` sets coordinates at the center of the buildings in the `ArcGSISceneLayer` to give the impression that the scene is centered on the location the user tapped.
 3. Set the `translationFactor` such that the user can view the entire scene by moving the device around it. The translation factor defines how far the virtual camera moves through the scene when the physical camera moves.
    -A good formula for determining translation factor to use in a tabletop map experience is translationFactor = sceneWidth / tableTopWidth. The scene width is the width/length of the scene content you wish to display in meters. The tabletop width is the length of the area on the physical surface that you want the scene content to fill. For simplicity, the sample assumes a scene width of 800 meters.