Merge pull request #27 from mdwigley/issue#25

#25 Fixed component name

Author: mdwigley

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-# Quick Start<a id="quick-start"></a>
+# Contributing
 * [How to Open a Bug Report](#how-to-open-a-bug-report)
 * [When is it a Feature Request](#When-is-it-a-feature-request)
 * [How to Open a Feature Request](#how-to-open-a-feature-request)
@@ -50,7 +50,7 @@ When you have the next best feature for the PrefabLightmapping project you will
 ## How to Submit Documentation
 1. [Find an Issue](#how-to-find-documentation-tasks) to resolve
 2. [Fork](https://help.github.com/articles/fork-a-repo/) the [repository](https://github.com/Enterlucent/PrefabLightmapping/)
-3. [Create a new branch](https://help.github.com/articles/creating-and-deleting-branches-within-your-repository/) with the format 'issue#{issue-id}-{your-github-user}' _(ie issue#224-mdwigley)_
+3. [Create a new branch](https://help.github.com/articles/creating-and-deleting-branches-within-your-repository/) with the format 'issue#{issue-id}' _(ie issue#224)_
 4. Make any changes or additions to your new branch
     * Make sure to [keep your forks in sync](https://help.github.com/articles/syncing-a-fork/) with the original repository
     * If you find that you need help with implementation, ask to have the "Help Wanted" label added to the issue as well as seeking others on the [Discord](https://discord.com/invite/mWDHDqkzeR) server
@@ -64,7 +64,7 @@ When you have the next best feature for the PrefabLightmapping project you will
 1. Setup your [Development Environment](/docs//Dev.Env.Win10.md)
 2. [Find an issue](#how-to-find-programing-tasks) to resolve
 3. [Fork](https://help.github.com/articles/fork-a-repo/) the [repository](https://github.com/Enterlucent/PrefabLightmapping/)
-4. [Create a new branch](https://help.github.com/articles/creating-and-deleting-branches-within-your-repository/) with the format 'issue#{issue-id}-{your-github-user}' _(ie issue#224-mdwigley)_
+4. [Create a new branch](https://help.github.com/articles/creating-and-deleting-branches-within-your-repository/) with the format 'issue#{issue-id}' _(ie issue#224)_
 5. [Update](https://gist.github.com/gitaarik/8735255#keeping-your-submodules-up-to-date) sub-modules
 6. Make any changes or additions to your new branch
     * Make sure to [keep your forks in sync](https://help.github.com/articles/syncing-a-fork/) with the original repository

README.md

@@ -9,15 +9,15 @@ The current version requires Unity 2021.3+.
 ## Getting Started
 * [Quick Start](#quick-start "Quick Start") - Brief introduction to the package
 * [Support Questions](#how-to-open-a-support-question "Support Questions") - Check to see if any one else has had the same question.
-* [Bug Report](#how-to-submit-a-bug-report "Support Questions") - Check to see if any one else has had the same problem.
-* [Feature Requests](#how-to-open-a-feature-request "Support Questions") - Check to see if any one else has had the same idea.
+* [Bug Report](#how-to-open-a-bug-report "Bug Report") - Check to see if any one else has had the same problem.
+* [Feature Requests](#how-to-open-a-feature-request "Feature Requests") - Check to see if any one else has had the same idea.
 
 
 ## Quick Start
 
 ### Prefab Lightmap Tool
 
-Place your prefabs in the scene with the PrefabLightmap component at their root. Set up your lighting in the editor and use the tool's interface (Window->Rendering->Lighting->Prefab Lightmap Tool) to bake your scene. After the bake is complete you can now spawn your prefabs in different scenes and they will use the light-mapping from the original scene.
+Place your prefabs in the scene with the PrefabLightmapData component at their root. Set up your lighting in the editor and use the tool's interface (Window->Rendering->Lighting->Prefab Lightmap Tool) to bake your scene. After the bake is complete you can now spawn your prefabs in different scenes and they will use the light-mapping from the original scene.
 
 *Remember that if you are not instantiating your prefabs at runtime you should remove the static flag from the GameObjects, otherwise static batching will mess with uvs and the lightmap won't work properly.*
 

docs/USAGE.md

@@ -23,10 +23,10 @@ The user interface is broken down into 4 distinct sections:
 2. Lightmap Bake Slot - Slots are named containers for storing different environmental bakes
 	- The name of the slot to bake for. *By default the "Default" slot is used*
 	- The check box disables the default slot name and allows the user to input a custom name for the slot to bake to.
-	- The button allows for manual "PrefabLightmap ListView" refreshing, however, *the "PrefabLightmap ListView" is also updated when the tool gains focus*
-3. PrefabLightmap ListView - Used to select which objects to bake for that have the PrefabLightmap component added to them
+	- The button allows for manual "PrefabLightmapData ListView" refreshing, however, *the "PrefabLightmapData ListView" is also updated when the tool gains focus*
+3. PrefabLightmapData ListView - Used to select which objects to bake for that have the PrefabLightmapData component added to them
 4. Misc Functions
-	- The initial check box will allow the user to quickly check or uncheck all items in the "PrefabLightmap ListView"
+	- The initial check box will allow the user to quickly check or uncheck all items in the "PrefabLightmapData ListView"
 	- The clear button will remove the lightmap slot information and stored data for the selected objects and the value of the "Lightmap Bake Slot"
 	- Bake a new lightmap environment and add it to the "Lightmap Bake Slot" and export the files to the "Export Location"
 
@@ -39,11 +39,11 @@ This section will provide an example workflow that uses the Prefab Lightmap Tool
 	- Ensure that lightmap UVs are setup, not overlapping and have good coverage
 	- Adjust Render component's lighting options to suit the needs of environment
 	- Add lights that are set to either "Bake" or "Mixed" mode
-2. Add the PrefabLightmap component
+2. Add the PrefabLightmapData component
 3. Open the Prefab Lightmap Tool (Rendering->Lighting->Prefab Lightmap Tool)
 	- [Optional] Set the export location
 	- [Optional] Change the slot name
-4. Select all the objects in the "PrefabLightmap ListView" to bake for
+4. Select all the objects in the "PrefabLightmapData ListView" to bake for
 5. Press the "Bake" button and wait for the bake to complete
 6. If alternate baking is needed, restart the process but give the slot a new name
 
@@ -56,7 +56,7 @@ Here we will provide some details on how the tool performs its work.
 
 * The export path must be relative to the projects asset folder so that the AssetDatabase functions can perform their work.  *The tool will **attempt** to keep you from using a folder outside the project's asset folder, however, this is not foolproof.*
 
-### PrefabLightmap ListView
+### PrefabLightmapData ListView
 
 * Uses the GameObject instance id for session object identification.   Should be able to retain selections after hierarchy modification but will not retain the selection values on scene change or on editor restart.