Describe how a module publishes a type set precisely

The Object section said each file in a module's types directory
contributes to the module's type set, which implies the set is assembled
automatically. It is not: OpenVox loads a module's type set from an
explicit declaration, which loader_paths.rb and module_loaders.rb resolve
as <module>::init_typeset. Name the file instead.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Michael Harp <mike@mikeharp.com>

Author: miharp

docs/_openvox_8x/lang_data_abstract.md

@@ -468,14 +468,17 @@ notice($g.greeting)    # hello
 notice($g =~ $greeter) # true
 ```
 
-In practice you rarely write this form inline. Modules declare object types in their `types` directory,
-where each file contributes to the module's type set.
+In practice you rarely write this form inline. Modules declare object types in their `types` directory, one
+type per file.
 
 ### `TypeSet`
 
 The `TypeSet` data type groups several object types together under one name and version, so a module can
-publish a related family of types. Type sets are declared in a module's `types` directory rather than
-written inline in a manifest, and they record a name, a version, and the types they contain.
+publish a related family of types rather than a loose collection. A type set records a name, a version, and
+the types it contains.
+
+A module publishes one by declaring it in `types/init_typeset.pp`, which OpenVox loads as the type set named
+after the module. Type sets are not written inline in a manifest.
 
 The type parser accepts any capitalization, so `Typeset` also works, but `TypeSet` is the spelling OpenVox
 itself uses when it renders the type.