chore(docs): correct markdown based on markdown lint#603
Conversation
|
awesome, while you're at it, could you also include this small fix here? The closing is invalid |
done. there is also general formatting issues with the json |
Codecov Report
@@ Coverage Diff @@
## develop #603 +/- ##
========================================
Coverage 99.95% 99.95%
========================================
Files 113 113
Lines 4535 4535
Branches 246 246
========================================
Hits 4533 4533
Partials 2 2 Continue to review full report at Codecov.
|
|
@heitorlessa - I run through all of the markdown files through vs code - markdownlint, see what you think |
|
1.8K changes hahaha perhaps we split into a separate PR so we know we experimented with markdown linting? |
Minimal changes here: #605 |
|
@heitorlessa i synced up the changes. So if you want to look at the impact this. I think once you have the linting working nicely. The impact will be less for future updates. |
|
Does it render correctly in the docs after all changes? and if you were to copy/paste the code snippets from docs, does it still work correctly e.g. indentation? Haven't had a chance to pull this PR and try these, so I'd trust if you say so and merge it ;) |
|
@heitorlessa - it does in my random testing. But I will have to think of a faster way to validate all of them. |
Issue #, if available:
Description of changes:
Changes:
https://awslabs.github.io/aws-lambda-powertools-python/latest/utilities/feature_flags/feature_flags.md*.mdfilesChecklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.