Update README.md

[farshaddavoudi]

Fix typos, problematic symbols and format, and some adjusting

Description

Please explain the changes you've made

Issue reference

We strive to have all PRs being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #[issue number]

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• The quickstart code compiles correctly
• You've tested new builds of the quickstart if you changed quickstart code
• You've updated the quickstart's README if necessary
• If you have changed the steps for a quickstart be sure that you have updated the automated validation accordingly. All of our quickstarts have annotations that allow them to be executed automatically as code. For more information see mechanical-markdown. For user guide with examples see Examples.

[paulyuk]

Please see one suggested tweak.

Also is there any change you could target this PR at the release-1.13 branch instead of master?

[paulyuk]

Hi @farshaddavoudi - something is wrong with the state management quickstart, so it won't pass checks anymore.

what i usually do is cd into that quickstart folder and do a make validate on my local machine to see if test will pass, or why not. do you have time to try?

[farshaddavoudi]

Hi @farshaddavoudi - something is wrong with the state management quickstart, so it won't pass checks anymore.

what i usually do is cd into that quickstart folder and do a make validate on my local machine to see if test will pass, or why not. do you have time to try?

Hi @paulyuk
I installed the Make utility and tried to figure out what's the root of the problem. As I perceived, the error message which a screenshot is attached, indicates that the make command is unable to execute the mm.py script, because it cannot find it. I searched / scanned for the script in the entire quickstart project without any luck. I don't know if I'm missing something or the script is erased somehow.

[paulyuk]

Hi @farshaddavoudi - something is wrong with the state management quickstart, so it won't pass checks anymore.
what i usually do is cd into that quickstart folder and do a make validate on my local machine to see if test will pass, or why not. do you have time to try?

Hi @paulyuk I installed the Make utility and tried to figure out what's the root of the problem. As I perceived, the error message which a screenshot is attached, indicates that the make command is unable to execute the mm.py script, because it cannot find it. I searched / scanned for the script in the entire quickstart project without any luck. I don't know if I'm missing something or the script is erased somehow.

Hi @farshaddavoudi sorry i did not include details about this. To do the local test you need Mechanical Marchdown which is a small utility found here: https://github.com/dapr/mechanical-markdown

To install you just do this:
pip3 install mechanical-markdown

Then that command should work well in each quickstart folder that has a makefile.

[paulyuk]

The test was failing because the dotnet build was not happening in order-processor subfolder. You could either set the working directory or cd into it.

However your simplification of restore and build made me think we should just further simplify. Dotnet language tools do a restore and build on run. So let's go straight to the run, which is done as a part of dapr run -f ..

[paulyuk]

This end step was missing, which was problematic for test framework.

[farshaddavoudi]

Hi @paulyuk, I apologize for not being able to participate and complete the job. I was busy preparing for my Azure certification exam. Thank you for approving my work.

[paulyuk]

LGTM