README.md:better markdown syntax for lists

[RandyMcMillan]

No description provided.

[RandyMcMillan]

This doesnt effect how README.md is rendered on GitHub.com.
It enables correct list rendering in other markdown clients.

[RandyMcMillan]

Before:

After:

[thunderbiscuit]

Good catch. When looking at it though I see a few more things that could be improved. Do you mind fixing these as well?

• The first 3 bullets under "This crate can be used for the..." can all be at the same level (the last 2 are not subpoints of the first one).
• The other list (Database Options, Blockchain Options, etc.) do not need indentation at the first level, and the second level can get 4 spaces of indentation.

Roughly I'd like us to try to adhere to the Google Markdown Styleguide, so that markdown is rendered the same everywhere. Thanks for catching this!

[RandyMcMillan]

6d84b96: update per suggestions

view rendered README.md: https://github.com/bitcoindevkit/bdk-cli/blob/6d84b9601a060e7765aaf819ad30a5201de14195/README.md

feel free to cherry-pick 6d84b96 and close if 854f072 isn't desirable.

[thunderbiscuit]

@RandyMcMillan if you can give me commit access to your PR I'll be able to push some small fixes and get this merged. I'm trying to clean up some of the PRs and move stuff along, sorry it's slow going.

It's apparently a small checkbox that says "Allow edits by maintainers".

[RandyMcMillan]

if there is something else I need to do - please tell me.

[thunderbiscuit]

Actually this will (I think) work, but in general you don't need to grant complete access to your repo for maintainers to be able to push commits on a PR.

I think this is the article to take a look at: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork

[thunderbiscuit]

ACK 7c2dc52. Thanks for the contribution!

[thunderbiscuit]

@notmandatory I don't have permissions to merge this because of the protections on the master branch. The PR currently fails the CI but this is a docs PR and I don't want to get into fixing all the pins on the dependencies here.

[notmandatory]

I think we need to do a couple things before we can merge this PR:

1. publish release bdk 0.29.1 which has MSRV fixes or just bump MSRV to 1.63 and fix CI in a 0.30.0 version
2. update bdk-cli to use bdk 0.29.1 and fix any other msrv issues