bluetooth: samples: grammatical fixes

[baaatli]

Fixed some of the grammatical errors and spelling mistakes in the README.rst file.

[kartben]

@baaatli is there a reason for closing/reopening new PRs? Anything we can do to help?

[baaatli]

Hi @kartben

Sorry, noobie Zephyrer here :)

I am learning to contribute on Zephyr. I missed some of the checks in the last PR I raised. I did not realise the things like ` before the reference links and hence closed the previous PRs to not waste your time reviewing it. I'll make sure to review them better before raising a PR the next time. Apologies for the inconvenience.

[kartben]

No worries:)
You can just keep your PR in draft mode until it's "green" and ready to be reviewed. You can force push amended commit to tour branch, no need to close/reopen all the time :)

[dipakgmx]

Hi @baaatli, could you please squash your commits.

[zephyrbot]

The following west manifest projects have changed revision in this Pull Request:

Name	Old Revision	New Revision	Diff
hal_nxp	zephyrproject-rtos/hal_nxp@0ea9c65	zephyrproject-rtos/hal_nxp@d291bdc (master)	zephyrproject-rtos/[email protected]

✅ All manifest checks OK

Note: This message is automatically posted and updated by the Manifest GitHub Action.

[baaatli]

@dipakgmx done!

( some mishap in between, sorry :) )

[jhedberg]

Looks generally fine to me - just a small whitespace issue I commented on separately inline

[jhedberg]

Please squash the two commits into a single one

[jhedberg]

What's this? Doesn't seem related to any language fixes.

[baaatli]

idk where this stemmed from. I didn't change anything in this file.

I did this to squash commits. Maybe this squashed a different commit.

git fetch git reset --soft HEAD~2 git commit git push -f

[baaatli]

I think this is too much effort for you folks to have so many reviews for such a small change. I will close this PR, raise a new one in draft mode and make sure it passes the pipeline before raising it for your review. Thanks for your time.

[dipakgmx]

You can drop that commit and then the PR is good.

[jhedberg]

@baaatli when you have just a single commit, you can update it simply using git commit --amend. You can always check the content what you're about to push using e.g. git show (for just a single commit) or e.g. git log -p upstream/main... Also, no need to close this PR and create a new one. Just fix up your local tree, and once you've verified that everything is fine do another git push --force.