docs: suggested changes 2

Author: Kawron

docs/creating_parsers/index.md

@@ -9,6 +9,7 @@ This and subsequent sections describe how to create new parsers. SC4S parsers pe
 
 * Make sure you have read our [contribution standards](../CONTRIBUTING.md).
 * Obtain a raw log message that you want to parse. If you do not know how to do it, refer to [Obtain raw message events](../troubleshooting/troubleshoot_resources.md#obtain-raw-message-events).
+* Create a new branch in the repository where you will apply your changes.
 * Prepare your testing environment. With Python>=3.11.0:
 
 ```
@@ -20,7 +21,7 @@ poetry install
 
 ### Naming conventions and project structure
 
-Parsers are .conf files with the naming convention: `app-type-vendor_product.conf`. Parsers that are part of the repository can be found at `package/etc/conf.d/conflib` or `package/lite/etc/addons` for Lite package. If you want to add locally new parser, you can add it to `/opt/sc4s/local` directory on your existing SC4S installation.
+Parsers are .conf files with the naming convention: `app-type-vendor_product.conf`. Parsers that are part of the repository can be found at `package/etc/conf.d/conflib` or `package/lite/etc/addons` for Lite package. Remember that adding your parser to the main or lite package in the repo requires building a new image for it to become available to your SC4S instance. If you want to add locally new parser, you can add it to `/opt/sc4s/local` directory on your existing SC4S installation.
 
 ### Parser structure
 
@@ -38,4 +39,15 @@ The application filter will match all messages that start with the string `Carbo
 
 ![](../resources/images/parser_dev_basic_output.png)
 
-To learn more about creating filters and parse blocks see pages: [Filter Messages](filter_message.md) and [Parse Messages](parse_message.md).
+To learn more about creating filters and parse blocks see pages: [Filter Messages](filter_message.md) and [Parse Messages](parse_message.md).
+
+### Adding parser to SC4S Lite package
+
+For SC4S lite, parsers are grouped into `addons`. Create a folder (if it doesn't already exist) in `package/lite/etc/addons` with the name of vendor. In this folder also create an `addon_metadata.yaml` file with vendor name:
+
+```
+---
+name: "<vendor_name>"
+```
+
+Lastly, add this addon to `package/lite/etc/config.yaml`.

docs/creating_parsers/parse_message.md

@@ -52,7 +52,7 @@ rewrite {
 
 ## Templates
 
-The `template` parameter in `r_set_splunk_dest_default` controls what part of the message is forwarded to Splunk. Templates are defined in `package/etc/conf.d/conflib/_common/t_templates.conf`. The most common ones:
+The `template` parameter in `r_set_splunk_dest_default` controls what part of the message is forwarded to Splunk. Templates are defined in [`package/etc/conf.d/conflib/_common/t_templates.conf`](https://github.com/splunk/splunk-connect-for-syslog/blob/main/package/etc/conf.d/conflib/_common/t_templates.conf). The most common ones:
 
 | Template | Content | Use case |
 |---|---|---|