Skip to content

Commit 95d5982

Browse files
committed
Pacify markdown-lint
Signed-off-by: Matthias Büchse <[email protected]>
1 parent bcb42e3 commit 95d5982

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

contributor-docs/development/tests/conformance-tests-sonobuoy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ In general, SCS tests for KaaS are derived from standards that define certain ex
7070
As an example for this step-by-step guide, let's assume a scenario in which there is a fictional standard called "scs-0299-v1-example-standard.md".
7171
Pretend that the fictitious standard here stipulates that at least one pod MUST run in the namespace "namespace-test-a".
7272

73-
> [!NOTE]
73+
> [!NOTE]
7474
> The functions and behaviors to be tested MUST be precisely defined in a standard.
7575
> If you as a developer want to test something that you think is best tested but is not yet part of any standard, you MUST update the standard accordingly.
7676
@@ -195,7 +195,7 @@ make dev-clean
195195
make dev-purge
196196
```
197197

198-
### (optional) Run all at once:
198+
### (optional) Run all at once
199199

200200
In addition, you can trigger all processes from above with one command. There is a single target in the Makefile for this:
201201

0 commit comments

Comments
 (0)