Update with custom components issues scope

README.md

@@ -57,13 +57,25 @@ input_scroll_down = scroll_down
 
 By default, **Druid** will auto-capture input focus, if any input component will be created. So you don't need to call `msg.post(".", "acquire_input_focus")`
 
-If you don't need this behaviour, you can disable it by settings `druid.no_auto_input` field in _game.project_:
+If you don't need this behaviour, you can disable it by setting `druid.no_auto_input` field in _game.project_:
 ```
 [druid]
 no_auto_input = 1
 ```
 
 
+### Template name check [optional]
+
+By default, **Druid** will auto check the parent component template name to build the full template name for component.
+
+If for some reason you want to pass the full template name by yourself, you can disable it by setting `druid.no_auto_template` field in _game.project_:
+
+```
+[druid]
+no_auto_template = 1
+```
+
+
 ### Stencil check [optional]
 
 When creating input components inside stencil nodes, you probably will use `component:set_click_zone()` to restrict clicks outside this stencil zone.
@@ -73,6 +85,7 @@ Druid can do it automatically on _late_init_ component step. To enable this feat
 stencil_check = 1
 ```
 
+
 ### Code [optional]
 
 Adjust **Druid** settings, if needed:
@@ -120,7 +133,7 @@ druid.on_window_callback(event)
 
 - **[Swipe](docs_md/01-components.md#swipe)** - System Druid component, handle swipe gestures on node
 
-- **[Drag](docs_md/01-components.md#drag)** - System Druid component, handle drag input on node 
+- **[Drag](docs_md/01-components.md#drag)** - System Druid component, handle drag input on node
 
 **Druid** also provides the following *extended* components:
 
@@ -265,11 +278,6 @@ You can fund the full **Druid** documentation here:
 https://insality.github.io/druid/
 
 
-## Games powered by Druid
-
-_You published your game and you using Druid? Note me!_
-
-
 ## License
 
 - Developed and supported by [Insality](https://github.com/Insality)