Apply suggestions from code review

Co-authored-by: Heitor Tashiro Sergent <[email protected]>

Author: yorugac

docs/maintenance.md

@@ -1,6 +1,6 @@
 # Maintenance of k6 Operator
 
-Just as with any project, k6 Operator requires regular maintenance updates to stay up-to-date with the changes and patches. There are several types of maintenance updates in this project, and they need to be addressed at different frequencies. Let's take a closer look at each of them.
+Just as with any project, k6 Operator requires regular maintenance updates to stay up-to-date with any changes and patches. There are several types of maintenance updates in this project, and they need to be addressed at different frequencies. Let's take a closer look at each of them.
 
 ## Update of dependencies
 

docs/release-workflow.md

@@ -1,10 +1,10 @@
 ## Release workflow
 
-Current release process is rather heavy on manual interventions:
+The current release process is rather heavy on manual interventions:
 
 1. _manual_ Create a Github release.
 2. "Release" workflow is triggered:
-- build of new Docker images from `main`
+- Build new Docker images from `main`
 - PR to update bundle
 3. _manual_ Review and merge PR with bundle update.
 4. _manual_ Commit and push the following changes:
@@ -24,4 +24,4 @@ Current release process is rather heavy on manual interventions:
 
 ### Errors on release
 
-Currently, if Helm JSON schema is not up-to-date, the Helm release will fail. [`helm-release.yaml` workflow](https://github.com/grafana/k6-operator/blob/main/.github/workflows/helm-release.yaml) will create a PR with the necessary changes and `exit 1` to force the maintainer to review the changes and re-run the release workflow.
+Currently, if the Helm JSON schema is not up-to-date, the Helm release will fail. [`helm-release.yaml` workflow](https://github.com/grafana/k6-operator/blob/main/.github/workflows/helm-release.yaml) will create a PR with the necessary changes and `exit 1` to force the maintainer to review the changes and re-run the release workflow.

docs/releases.md

@@ -80,7 +80,7 @@ The `main` branch of the k6 Operator should be seen as a development branch. It
 
 We do not commit to any stability guarantees of Golang interfaces at this point in time. However, in practice, the [Golang package for CRD types](https://github.com/grafana/k6-operator/tree/main/api/v1alpha1) is closely tied to changes in CRD and follows the same guidelines as the corresponding CRD type.
 
-### How release is done
+### Release process
 
 Release procedure is fully described in the [internal docs](https://github.com/grafana/k6-operator/blob/main/docs/release-workflow.md).