Closed GincyAG closed 1 year ago
The following issues were identified:
document/6-Appendix/F-Leveraging_Dev_Tools.md:248 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- URL encode: encodeURI()
& ..."]
document/6-Appendix/F-Leveraging_Dev_Tools.md:249 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Above] [Context: "## Responsive Design Mode"]
The following mistakes were identified:
/home/runner/work/wstg/wstg/document/6-Appendix/F-Leveraging_Dev_Tools.md 246:47 ✖ Incorrect usage of the term: “Base64”, use “base64” instead terminology 246:156 ✖ Incorrect usage of the term: “Base64”, use “base64” instead terminology 246:188 ✖ Incorrect usage of the term: “Base64”, use “base64” instead terminology
The following issues were identified:
document/6-Appendix/F-Leveraging_Dev_Tools.md:248 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- URL encode: encodeURI()
& ..."]
document/6-Appendix/F-Leveraging_Dev_Tools.md:249 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Above] [Context: "## Responsive Design Mode"]
The following mistakes were identified:
/home/runner/work/wstg/wstg/document/6-Appendix/F-Leveraging_Dev_Tools.md 246:47 ✖ Incorrect usage of the term: “Base64”, use “base64” instead terminology 246:156 ✖ Incorrect usage of the term: “Base64”, use “base64” instead terminology 246:188 ✖ Incorrect usage of the term: “Base64”, use “base64” instead terminology
No need to close. We know pre-existing issues come up sometimes, you can just tackle them, no big deal.
This PR covers issue #1070 .
What did this PR accomplish?
Thank you for your contribution!