add some information how to run markdown tests with a different runtime

Signed-off-by: Filinto Duran <[email protected]>

Author: filintod

README.md

@@ -120,12 +120,20 @@ tox -e type
 
 8. Run examples
 
-The tests in examples are using Mechanical Markdown (MM) from https://github.com/dapr/mechanical-markdown.
-
 ```bash
 tox -e examples
 ```
 
+[Dapr Mechanical Markdown](https://github.com/dapr/mechanical-markdown) is used to test the examples.
+
+If you need to run the examples against a development version of the runtime, you can use the following command:
+- Get your daprd runtime binary from [here](https://github.com/dapr/dapr/releases) for your platform.
+- Copy the binary to a folder, for example `examples/.dapr/bin/` directory.
+- In your example README, change the `dapr run` command and add a line `--runtime-path ./examples \`.
+- Copy a dapr config file `config.yaml` file to the `examples/.dapr` directory.  This file is usually in your $(HOME)/.dapr directory if you had installed dapr cli before.
+- Now you can run the example with `tox -e examples`.
+
+
 ## Documentation
 
 Documentation is generated using Sphinx. Extensions used are mainly Napoleon (To process the Google Comment Style) and Autodocs (For automatically generating documentation). The `.rst` files are generated using Sphinx-Apidocs.

examples/conversation/README.md

@@ -20,6 +20,11 @@ The Conversation API supports real LLM providers including:
    ```
 
 2. **Run the simple conversation on the Alpha V1 version (dapr 1.15)**
+
+   This is a basic example that uses the Conversation API to get a response from a bot.
+   It also uses the `echo` provider that just echoes back the message.
+   In the echo provider, a multi-input message is returned as a single output separated by newlines.
+
     <!-- STEP
     name: Run Conversation Alpha V1
     expected_stdout_lines: