Merge pull request #157 from chmeliik/accelerator-week-updates

Miscellaneous fixes

docs/modules/ROOT/pages/advanced-how-tos/releasing/tenant-release-pipelines.adoc

@@ -3,7 +3,7 @@
 The usual release process in {ProductName} involves two different teams: a *Development team* and a *Managed environment team* as described in
 xref:/advanced-how-tos/releasing/index.adoc[Releasing an application]. But, sometimes the Development team wants to release their software to some destination that is directly under their control, using their own secrets, without depending on a Managed environment team. In {ProductName} we call this model a *tenant release pipeline*. It's a release pipeline that runs in the tenant namespace of the Development team, rather than in that of the Managed environment team.
 
-The gist here is that you are going to follow the regular instructions to xref:/advanced-how-tos/releasing/create-release-plan.adoc[create a ReleasePlan], but you will omit the `target` and specify the `pipelineRef` directly on your `ReleasePlan`.
+The gist here is that you are going to follow the regular instructions to xref:/advanced-how-tos/releasing/create-release-plan.adoc[create a ReleasePlan], but you will omit the `target` and specify the `pipeline` directly on your `ReleasePlan`.
 
 
 .*Prerequisites*
@@ -43,16 +43,17 @@ spec:
        - name: demo-component-2
          repository: registry/destination-image-repository-2
          tags: [latest]
- pipelineRef: <.>
-   resolver: git
-   params:
-     - name: url
-       value: "https://github.com/konflux-ci/release-service-catalog.git"
-     - name: revision
-       value: production
-     - name: pathInRepo
-       value: "pipelines/push-to-external-registry/push-to-external-registry.yaml"
- serviceAccont: appstudio-pipeline <.>
+ pipeline:
+   pipelineRef: <.>
+     resolver: git
+     params:
+       - name: url
+         value: "https://github.com/konflux-ci/release-service-catalog.git"
+       - name: revision
+         value: production
+       - name: pathInRepo
+         value: "pipelines/push-to-external-registry/push-to-external-registry.yaml"
+   serviceAccountName: appstudio-pipeline <.>
 ----
 
 +

docs/modules/ROOT/pages/how-tos/configuring/creating-secrets.adoc

@@ -59,7 +59,7 @@ When building content from GitHub, you will need to install an application for P
 
 . In GitLab select your avatar, then select **Edit profile** > **Access Tokens** > **Add new token**.
 . Select the following scopes: `api`, `read_repository`, and `write_repository`.
-. Optional: If your GitLab instance supports setting token role, set a role to `Maintainer`.
+. If your GitLab instance supports setting token roles, set the role to `Maintainer`.
 . Select **Create personal access token**.
 . Add a token to your {ProductName} workspace by running the `kubectl create` command and creating a new YAML file with a secret:
 
@@ -102,7 +102,7 @@ apiVersion: v1
 kind: Secret
 metadata:
   name: pipelines-as-code-secret
-  namespace: <YOUR NAMESPACE>-tenant
+  namespace: <YOUR NAMESPACE>
   labels:
     appstudio.redhat.com/credentials: scm
     appstudio.redhat.com/scm.host: <source-control-management-host> # for example, gitlab.com