Integrating github/staging through commit 5f214be

Gems/SceneLoggingExample/Code/CMakeLists.txt

@@ -21,8 +21,6 @@ ly_add_target(
     INCLUDE_DIRECTORIES
         PRIVATE
             .
-        PUBLIC
-            Include
     BUILD_DEPENDENCIES
         PUBLIC
             AZ::AzCore
@@ -38,8 +36,6 @@ ly_add_target(
     INCLUDE_DIRECTORIES
         PRIVATE
             .
-        PUBLIC
-            Include
     BUILD_DEPENDENCIES
         PRIVATE
             Gem::SceneLoggingExample.Static

Gems/SceneLoggingExample/ReadMe.txt

@@ -1,12 +1,12 @@
 The Scene Logging Example demonstrates how to extend the SceneAPI by adding additional logging to the pipeline. The SceneAPI is 
-a collection of libraries that handle loading scene files and converting content to data that the Lumberyard engine and editor can load. 
+a collection of libraries that handle loading scene files and converting content to data that the Open 3D Engine and its editor can load. 
 
 The following approach is used:
     1. The FbxSceneBuilder and SceneData load and convert the scene file (for example, .fbx) into a graph that is stored in memory. 
     2. SceneCore and SceneData are used to create a manifest with instructions about how to export the file. 
     3. SceneData analyzes the manifest and memory graph and creates defaults.
     4. Scene Settings allows updates to the manifest through a UI.
-    5. The ResourceCompilerScene uses the instructions from the manifest and the data in the graph to create assets. These assets are ready for Lumberyard to use.
+    5. The ResourceCompilerScene uses the instructions from the manifest and the data in the graph to create assets. These assets are ready for Open 3D Engine to use.
 
 The example gem demonstrates the following key features:
     - Initialization of the SceneAPI libraries.