Minor clean up; moving around information in the 'out-of-scope' section

Signed-off-by: AMZN-Gene <[email protected]>

Author: AMZN-Gene

rfcs/RFC Feature - USD in the Scene Pipeline.md

@@ -505,9 +505,10 @@ For our initial deliverable, we will generate basic O3DE physically based render
 
 However, the options for shaders and materials from USD files are much bigger than that. As we wrap up our first set of work to support USD, we'll want to start planning what a more fully featured material and shader pipeline from USD files could look like.
 
-Extra USD Properties and O3DE Components
+
+USD Property -> O3DE Component Converter
 ------------------------------
-Allow developers to read generic scene information, and inject custom components into the procedural prefabs generated by importing USD files. O3DE would ship with built-in components. 
+Allow developers to read generic scene information, and inject custom components into the procedural prefabs generated by importing USD files. 
 1.  Update Assimp to output USD property data
         1.  Assimp::Scene root "kitchen"
             1.  child 01
@@ -518,10 +519,8 @@ Allow developers to read generic scene information, and inject custom components
                 5.  NEW: Other user data/properties/overrides
 
 1.  O3DE scene system already supports storing generic info into each scene node
+1.  Provide developers with a way to add to the procedural prefabs recipe, one example we could ship with is an editor component for variant selection dropdown. It allow designers to select from a list of available variants from within the editor when a variant set is included in a USD
 
-Editor Variant Selection Dropdown 
-------------------------------
-Allow designers to select from a list of available variants from within the editor when a variant set is included in a USD
 
 Convert O3DE prefabs to USD files
 ---------------------------------
@@ -533,7 +532,7 @@ This is something that could be looked at long term.
 FAQ
 ===
 
-Why not stop after phase 2: just treat USD like other formats, flatten everything, and then generate product assets?
+Why not just treat USD like other formats, flatten everything, and then generate product assets?
 --------------------------------------------------------------------------------------------------------------------
 
 By expanding USD support to create a prefab hierarchy that mimics the USD relationship graph, we will see two main areas of benefit: