update commit prev

docs/provider_authoring.md

@@ -84,7 +84,7 @@ class MyTableProvider(TableProviderMixin, Provider):
         return self.search_table_from_url(url, limit=limit)
 ```
 
-`TableProviderMixin.search_table_from_url` returns `ProviderCore.base.SearchResult` entries. If you want to integrate this plugin with the strict `ResultTable` registry, add a small adapter that converts `SearchResult` -> `ResultModel` and register it using `register_plugin` (see `Provider/vimm.py` for a real example).
+`TableProviderMixin.search_table_from_url` returns `ProviderCore.base.SearchResult` entries. If you want to integrate this plugin with the strict `ResultTable` registry, add a small adapter that converts `SearchResult` -> `ResultModel` and register it using `register_plugin` (see `plugins/vimm/__init__.py` for a real example).
 
 ---
 
@@ -115,7 +115,7 @@ class MyTableProvider(TableProviderMixin, Provider):
 
 ```py
 from SYS.result_table_adapters import get_provider
-from Provider import example_provider
+from plugins import example_provider
 
 
 def test_example_provider_registration():
@@ -132,10 +132,10 @@ def test_example_provider_registration():
 
 ## References & examples
 
-- Read `Provider/example_provider.py` for a compact example of a strict adapter and dynamic columns.
-- Read `Provider/vimm.py` for a table-provider that uses `TableProviderMixin` and converts `SearchResult` → `ResultModel` for registration.
+- Read `plugins/example_provider.py` for a compact example of a strict adapter and dynamic columns.
+- Read `plugins/vimm/__init__.py` for a table-provider that uses `TableProviderMixin` and converts `SearchResult` → `ResultModel` for registration.
 - See `docs/provider_guide.md` for a broader provider development checklist.
 
 ---
 
-If you want, I can also add a small `Provider/myprovider_template.py` file and unit tests for it — say the word and I'll add them and wire up tests. 🎯
+If you want, I can also add a small `plugins/myprovider_template.py` file and unit tests for it.