docs/naming-conventions/in-file-prefixes.md

@@ -6,11 +6,11 @@ We only have 3 separators to work with, so we try keep their meaning consistent
 `_` : Used instead of spacebar in composite words, eg. `eifel_tower_base`.  
 `.` : Suffixes, used only for symmetry sides, ie `.L`/`.R`, and for variations, `clock.normal`, `clock.broken`, `clock.destroyed`  
 
-## Asset Mnemonic
+## Asset Identifier
 
-All local datablocks across all assets of a production must have a unique name. To faciliate this, each asset is assigned a mnemonic that must remain unique within a given production. For example, a character named "Elder Sprite" might get the mnemonic "ES". The max length of this mnemonic is not limited, but the shorter the better. If a minor prop in the production is called "Electric Switch", it can not have the mnemonic "ES", because it's already taken. So, "ELSW" would be fine. 
+All local datablocks across all assets of a production must have a unique name. To faciliate this, each asset is assigned an identifier that must remain unique within a given production. For example, a character named "Elder Sprite" might get the identifier "ES". The max length of this identifier is not limited, but the shorter the better. If a minor prop in the production is called "Electric Switch", it can not have the identifier "ES", because it's already taken. So, "ELSW" would be fine. 
 
-This mnemonic will be used in the names of datablocks, to make sure all names are unique, not just in a single file, but the whole production. This is useful/necessary because of the way Blender's Override system works, which relies on making local copies of linked object hierarchies, meaning all assets need to be able to exist in the same namespace without collisions.
+This identifier will be used in the names of datablocks, to make sure all names are unique, not just in a single file, but the whole production. This is useful/necessary because of the way Blender's Override system works, which relies on making local copies of linked object hierarchies, meaning all assets need to be able to exist in the same namespace without collisions.
 
 ## Asset Collections
 
@@ -27,7 +27,7 @@ Example: `CH-elder_sprite`
 
 Note that there's no technical distinction between different types of assets. This is purely for organizational purposes and comfort.
 
-The immediate sub-collections of the root collection are strictly defined by our Asset Pipeline add-on, as being `{mnemonic}-{task_layer}`. Task Layers are the different data layers that make up an asset, such as Modeling, Rigging, and Shading. Inside these Task Layer Collections, each artist responsible for their own Task Layer may create sub-collections freely, as long as each sub-collection still starts with `{mnemonic}-{task_layer}-`.
+The immediate sub-collections of the root collection are strictly defined by our Asset Pipeline add-on, as being `{identifier}-{task_layer}`. Task Layers are the different data layers that make up an asset, such as Modeling, Rigging, and Shading. Inside these Task Layer Collections, each artist responsible for their own Task Layer may create sub-collections freely, as long as each sub-collection still starts with `{identifier}-{task_layer}-`.
 So, here's what an asset's collection hierarchy might look like:
 ```txt
 CH-elder_sprite
@@ -44,7 +44,7 @@ CH-elder_sprite
 ```
 
 ## Asset Datablocks
-- All local datablocks of an asset (Object, Mesh, Material, Action, etc.) must include either the asset's mnemonic or full name (both is not necessary). Eg., `RIG-elder_sprite` or `GEO-ES-eye.L`. This is automated by the Asset Pipeline add-on.
+- All local datablocks of an asset (Object, Mesh, Material, Action, etc.) must include either the asset's identifier or full name (both is not necessary). Eg., `RIG-elder_sprite` or `GEO-ES-eye.L`. This is automated by the Asset Pipeline add-on.
 - Object Data and Shape Keys should be named the same as the containing Object. This is automated by the Asset Pipeline add-on.
 - Datablock names must not end with a `.00x` suffix. This is enforced by the Asset Pipeline add-on.
     - When there's too many objects to manually name, like when building a house out of a hundred wooden plank objects, the **Batch Rename Datablocks** built-in add-on should be used to give groups of objects the same name. Then replace the `.` in the `.00x` suffixes with an `_` instead, so `GEO-HS-wooden_plank.023` becomes `GEO-HS-wooden_plank_023`.
@@ -99,7 +99,7 @@ Eyes_Surprised
 ```
 
 ### Rig Constraints
-Rigs may use Actions for Action Constraint based control set-ups. Since these are asset datablocks, they must start with the asset mnemonic.
+Rigs may use Actions for Action Constraint based control set-ups. Since these are asset datablocks, they must start with the asset identifier.
 Corrective Actions are ones which are meant to activate when two other actions activate. These should use the name of the two trigger actions, separated by a "+".
 
 Examples: 
@@ -110,7 +110,7 @@ RIG-ES-mouth_open+lips_wide
 ```
 
 ### Animations of Shots
-Actions created for shots should be named `ANI-{asset_mnemonic}-{scene_name}.{version}`
+Actions created for shots should be named `ANI-{asset_identifier}-{scene_name}.{version}`
 
 Examples:
 ```