docs: Improvements to the Labs page

From feedback giving after the first version of the page was merged. Signed-off-by: Gustavo Padovan <[email protected]>
kernelci · Jul 8, 2024 · ab5b71a · ab5b71a
1 parent d0df9fe
commit ab5b71a
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/kernelci.org/content/en/labs/_index.md b/kernelci.org/content/en/labs/_index.md
@@ -8,9 +8,11 @@ Anyone can connect their test labs to KernelCI. Once a lab is connected to Kerne
 
 It is up to each lab to define whether it will receive specific test configurations or a generic range of test jobs. If the lab is a LAVA lab, for example, the KernelCI [LAVA runtime](../api_pipeline/pipeline/connecting-lab) will generate test jobs for each single test that is configured to run. On the other hand, if a lab is implementing its own runtime (or bridge to Maestro APIs), they may choose to generate the individual test jobs themselves.
 
-If you are interested it just sending the results of test runs in your infrastructure, you should look at sending the data to [KCIDB](../kcidb) - KernelCI common database for results.
+If you are interested in just sending the results of test runs in your infrastructure, you should look at sending the data to [KCIDB](../kcidb) - KernelCI common database for results.
 
 There are a few ways labs can be connected to KernelCI. The documentation for connecting labs in the new architecture is evolving as we add labs.
 
 * [Connecting a LAVA lab](../api_pipeline/pipeline/connecting-lab)
-* Writing your own bride/runtime using Maestro APIs (TBD)
+* Writing your own bridge/runtime using Maestro APIs (doc TBD, see this [GitHub issue](https://github.com/kernelci/kernelci-project/issues/349#issuecomment-2097641023))
+
+We know that the documentation above may not answer all your questions. We are working to improve it. We ask you to reach out to our mailing list at [[email protected]](mailto:[email protected])  with questions and feedback. We are eager to hear from you!