Apply 1 suggestion(s) to 1 file(s)

content/guides/component_guide.md

@@ -607,7 +607,7 @@ Apertis main archive, a proper release needs to be issued.
 * Create a Merge Request based on your `wip/` branch for the most recent
   release branch where you want to land your changes:
   * for published stable release, the main branch (for instance
-    `apertis/v2019`) should **never** be targeted directly but updates and
+    `apertis/v2019`) should **never** be targeted directly, but updates and
     fixes should go through the `apertis/v2019-security` or
     `apertis/v2019-updates` branches, see [Process after a product
     release]( {{< ref "release-flow.md#process-after-a-product-release" >}} )