docs: Improve markdownlint configuration (#11104)

## Description

Closes: #9404



---

### Author Checklist

*All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.*

I have...

- [x] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [ ] added `!` to the type prefix if API or client breaking change
- [x] targeted the correct branch (see [PR Targeting](https://github.com/cosmos/cosmos-sdk/blob/master/CONTRIBUTING.md#pr-targeting))
- [x] provided a link to the relevant issue or specification
- [ ] followed the guidelines for [building modules](https://github.com/cosmos/cosmos-sdk/blob/master/docs/building-modules)
- [ ] included the necessary unit and integration [tests](https://github.com/cosmos/cosmos-sdk/blob/master/CONTRIBUTING.md#testing)
- [ ] added a changelog entry to `CHANGELOG.md`
- [ ] included comments for [documenting Go code](https://blog.golang.org/godoc)
- [ ] updated the relevant documentation or specification
- [x] reviewed "Files changed" and left comments if necessary
- [x] confirmed all CI checks have passed

### Reviewers Checklist

*All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.*

I have...

- [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [ ] confirmed `!` in the type prefix if API or client breaking change
- [ ] confirmed all author checklist items have been addressed 
- [ ] reviewed state machine logic
- [ ] reviewed API design and naming
- [ ] reviewed documentation is accurate
- [ ] reviewed tests and test coverage
- [ ] manually tested (if applicable)

x/epoching/spec/01_state.md

@@ -52,7 +52,7 @@ We execute epoch after execution of genesis transactions to see the changes inst
 
 ## Execution on epochs
 
-- Try executing the message for the epoch
-- If success, make changes as it is
-- If failure, try making revert extra actions done on handlers (e.g. EpochDelegationPool deposit)
-- If revert fail, panic
+* Try executing the message for the epoch
+* If success, make changes as it is
+* If failure, try making revert extra actions done on handlers (e.g. EpochDelegationPool deposit)
+* If revert fail, panic

x/epoching/spec/03_to_improve.md

@@ -8,10 +8,10 @@ order: 3
 
 Cases that trigger unbonding process
 
-- Validator undelegate can unbond more tokens than his minimum_self_delegation and it will automatically turn the validator into unbonding
+* Validator undelegate can unbond more tokens than his minimum_self_delegation and it will automatically turn the validator into unbonding
 In this case, unbonding should start instantly.
-- Validator miss blocks and get slashed
-- Validator get slashed for double sign
+* Validator miss blocks and get slashed
+* Validator get slashed for double sign
 
 **Note:** When a validator begins the unbonding process, it could be required to turn the validator into unbonding state instantly.
   This is different than a specific delegator beginning to unbond. A validator beginning to unbond means that it's not in the set any more.