UNI-4964: Final edits before Tech Review/PR

unitALG · unitALG · commit 4a987e7fd104 · 2019-05-23T21:50:59.000-04:00
diff --git a/com.unity.formats.fbx/Documentation~/exporting.md b/com.unity.formats.fbx/Documentation~/exporting.md
@@ -199,12 +199,11 @@ In addition, it also exports the following animated attributes:
 
 ## Export Options window
 
-When exporting an FBX file, the following Export Options window opens, displaying options for specifying what gets exported.
+When exporting an FBX file, the following **Convert Options** window opens, displaying options for specifying what gets exported.
 
 ![Export Options window](images/FBXExporter_ConvertOptionsWindow.png)
 
-
-### Export Options Properties
+### Convert Options Properties
 
 | Property:                 | Function:                                                    |
 | :------------------------ | :----------------------------------------------------------- |
diff --git a/com.unity.formats.fbx/Documentation~/knownissues.md b/com.unity.formats.fbx/Documentation~/knownissues.md
@@ -1,9 +1,9 @@
-# Known Issues
+# Limitations
 
 * The FBX Exporter package does not support exporting `.asset` files.
 
-* The bind poses of animated skinned meshes are lost on export. For example, if you export an animated skinned mesh from Unity and import it into Autodesk® Maya® and Autodesk® Maya LT™ you will not be able to set the character into the bind pose using the **Rigging** > **Skin** > **Go to Bind Pose** command.
+* The bind poses of animated skinned Meshes are lost on export. For example, if you export an animated skinned Mesh from Unity and import it into Autodesk® Maya® and Autodesk® Maya LT™, you will not be able to set the character into the bind pose using the **Rigging** > **Skin** > **Go to Bind Pose** command.
 
-* Name or path changes are ignored when converting a Model instance
+* The FBX Exporter package ignores name or path changes when converting a Model instance.
 
-* Exporting animation only for animated lights and cameras from Autodesk® Maya® and Maya LT™ is not currently supported
+* The FBX Exporter package does not support exporting animation only for animated Lights and Cameras from Autodesk® Maya® and Maya LT™.
diff --git a/com.unity.formats.fbx/Documentation~/prefabs.md b/com.unity.formats.fbx/Documentation~/prefabs.md
@@ -71,8 +71,7 @@ When converting to an FBX Linked Prefab, the following window opens, displaying
 
 ![Convert Options for an FBX Linked Prefab](images/FBXExporter_ConvertOptionsWindow.png)
 
-
-#### Convert Option Properties
+#### Convert Option properties
 
 | Property:                 | Function:                                                    |
 | :------------------------ | :----------------------------------------------------------- |
diff --git a/com.unity.formats.fbx/Documentation~/troubleshooting.md b/com.unity.formats.fbx/Documentation~/troubleshooting.md
@@ -1,46 +1,74 @@
 # Troubleshooting
 
 This section covers the following issues:
-    * [Upgrading the FBX Exporter from the Asset Store package](#AssetStoreToPackman)
-    * [Incorrect skinning on Animated Skinned Mesh](#SkinnedMeshExport)
-    * [Converting GameObjects with UI components](#ConvertUI)
-    * [Overwriting FBX files](#OverwritingFiles)
-    * [Tree primitive no longer editable after conversion](#EditableTree)
-    * [Trail and line particles lose material after being converted](#ParticlesLoseMaterial)
+
+* [Upgrading the FBX Exporter from the Asset Store package](#AssetStoreToPackman)
+* [Incorrect skinning on Animated Skinned Mesh](#SkinnedMeshExport)
+* [Converting GameObjects with UI components](#ConvertUI)
+* [Overwriting FBX files](#OverwritingFiles)
+* [Tree primitive no longer editable after conversion](#EditableTree)
+* [Trail and line particles lose material after being converted](#ParticlesLoseMaterial)
+
+
 
 <a name="AssetStoreToPackman"></a>
+
 ## Upgrading the FBX Exporter from the Asset Store package
 
-When installing a new version of the FBX Exporter package after using version 1.3.0f1 or earlier, the link between Assets and FbxPrefab components may be lost. See [Updating from 1.3.0f1 or earlier](index.md#Repairs_1_3_0f_1) for repairing instructions.
+When installing a new version of the FBX Exporter package after using version 1.3.0f1 or earlier, the link between Assets and Prefabs may be lost. To repair these problems, follow the instructions under [Updating from 1.3.0f1 or earlier](index.md#Repairs_1_3_0f_1).
+
+
 
 <a name="SkinnedMeshExport"></a>
 ## Incorrect skinning on Animated Skinned Mesh
 
-If animated skinned meshes do not export with the correct skinning, it may be because they are not in the bind pose on export.
-Before exporting the animated skinned mesh, check the following:
-* The skinned mesh animation is not being previewed in the Animation of Timeline windows, as this may cause issues on export
-* The original Rig's FBX does not contain animation
-    * It is currently not possible to fix this issue in Unity. Animation will first need to be separated from the Rig in a separate modeling software such as Autodesk® Maya®
+If animated skinned Meshes do not export with the correct skinning, it may be because they are not in the bind pose on export.
+
+Before exporting the animated skinned Mesh, make sure that:
+
+* The skinned mesh animation is not being previewed in the Animation of Timeline windows, as this may cause issues on export.
+
+* The original Rig's FBX does not contain animation. 
+    
+    **NOTE**: It is currently not possible to fix this issue in Unity. You need to separate your animation from the Rig in a separate modeling software such as Autodesk® Maya® first.
+
+
 
 <a name="ConvertUI"></a>
+
 ## Converting GameObjects with UI components
 
-Converting hierarchies with UI components (i.e. RectTransform) will break the UI.
-A workaround for this is to first prepare the hierarchy so that it has no GameObjects with UI elements before converting, then add the UI elements to the FBX Linked Prefab afterwards.
+Converting hierarchies with UI components (for example, **RectTransform**) breaks the UI. 
+
+To work around this: 
+
+1. Prepare the hierarchy so that it has no GameObjects with UI elements before converting.
+2. Add the UI elements to the FBX Linked Prefab afterwards.
+
+
 
 <a name="OverwritingFiles"></a>
 ## Overwriting FBX files
 
-In some situations, overwriting an FBX file that is used by an FBX Linked Prefab instance, may lead to unexpected results such as additional objects being added to the Prefab hierarchy.
-Therefore, we recommend not to overwrite an FBX file that is used by an FBX Linked Prefab.
-    
+In some situations, overwriting an FBX file used by an FBX Linked Prefab instance may lead to unexpected results, such as additional objects being added to the Prefab hierarchy. 
+
+For this reason, we recommend not to overwrite an FBX file that is used by an FBX Linked Prefab.
+
+
+
 <a name="EditableTree"></a>
+
 ## Tree primitive no longer editable after conversion
 
-Converting a Tree primitive will make the Tree no longer editable.
-Make sure to only convert the Tree when finished editing. Otherwise click undo after converting to return to previous state where the Tree was editable.
+Converting a Tree primitive makes the Tree read-only.
+
+To avoid this, make sure to convert only the Tree when finished editing. Otherwise, Undo the conversion to return to previous state where the Tree was editable.
+
+
 
 <a name="ParticlesLoseMaterial"></a>
-## Trail and line particles lose material after being converted
 
-If materials are lost when converting trail or line particles, the materials will currently need to be re-applied to the FBX Linked Prefab after conversion.
+## Trail and line particles lose Material after being converted
+
+If you lose Materials when converting trail or line particles, you need to re-apply the Materials to the FBX Linked Prefab after conversion.
+
