Hugo: Fix participating page (#8565)

The page was wrongly formatted:
* Two lists were shown as paragraphs, add empty lines so that they are
  parsed as lists.
* The list of members, reviewers was not intended properly, so that the
  single items are intended but not their description. Indent
  everything.
* Fix URL to owners.md file, the old one gives a 404.

content/en/docs/home/contribute/participating.md

@@ -57,8 +57,7 @@ Another reviewer or approver can remove a hold with the comment: `/hold cancel`.
     Approvers may skip further reviews for small pull requests if the proposed changes appear trivial and/or well-understood.
     An approver can indicate `/lgtm` or `/approve` in a PR comment to have a pull request merged, and all pull requests require at least one approver to provide their vote in order for the PR to be merged.
 
-{{< note  >}}
+    {{< note  >}}**Note:** There is a special case when an approver uses the comment: `/lgtm`. In these cases, the automation will add both `lgtm` and `approve` tags, skipping any further review.
-**Note:** There is a special case when an approver uses the comment: `/lgtm`. In these cases, the automation will add both `lgtm` and `approve` tags, skipping any further review.
     {{< /note  >}}
 
     For PRs that require no review (typos or otherwise trivial changes), approvers can enter an `lgtm` comment, indicating no need for further review and flagging the PR with approval to merge.
@@ -67,6 +66,7 @@ For PRs that require no review (typos or otherwise trivial changes), approvers c
 
 You can get an overview of [SIG Docs from the community github repo](https://github.com/kubernetes/community/tree/master/sig-docs). 
 The SIG Docs group defines two teams on Github:
+
  - [@kubernetes/sig-docs-maintainers](https://github.com/orgs/kubernetes/teams/sig-docs-maintainers)
  - [@kubernetes/sig-docs-pr-reviews](https://github.com/orgs/kubernetes/teams/sig-docs-pr-reviews)
 
@@ -76,16 +76,18 @@ Both can be referenced with their `@name` in github comments to communicate with
 These teams overlap, but do not exactly match, the groups used by the automation tooling.
 For assignment of issues, pull requests, and to support PR approvals, the automation uses information from the OWNERS file.
 
-To volunteer as a reviewer or approver, make a pull request and add your Github handle to the relevant section in the [OWNERS file](https://github.com/kubernetes/community/blob/master/contributors/devel/owners.md).
+To volunteer as a reviewer or approver, make a pull request and add your Github handle to the relevant section in the [OWNERS file](https://github.com/kubernetes/community/blob/master/contributors/guide/owners.md).
 
 {{< note  >}}
 **Note:** Reviewers and approvers must meet requirements for participation.
 For more information, see the [Kubernetes community](https://github.com/kubernetes/community/blob/master/community-membership.md#membership) repository.
 {{< /note  >}}
 
-Documentation for the [OWNERS](https://github.com/kubernetes/community/blob/master/contributors/devel/owners.md) explains how to maintain OWNERS for each repository that enables it.
+Documentation for the [OWNERS](https://github.com/kubernetes/community/blob/master/contributors/guide/owners.md)
+explains how to maintain OWNERS for each repository that enables it.
 
 The [Kubernetes website repository](https://github.com/kubernetes/website) has two automation (prow) [plugins enabled](https://github.com/kubernetes/test-infra/blob/master/prow/plugins.yaml#L210):
+
 - blunderbuss
 - approve