diff options
| author | guineveresaenger <guineveresaenger@github.com> | 2019-03-14 10:07:27 -0700 |
|---|---|---|
| committer | guineveresaenger <guineveresaenger@github.com> | 2019-03-14 10:07:27 -0700 |
| commit | 158feaf8f758372b3ea5af18c6832cc5ee2d927c (patch) | |
| tree | 63abbd95322c8f5a0a4009af7a8b754d2ef7fdce | |
| parent | c25d393d5276080c1ab2512202422b7341f99e05 (diff) | |
change depth of content and ToC
| -rw-r--r-- | contributors/guide/README.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/contributors/guide/README.md b/contributors/guide/README.md index a704ed2d..ca90d442 100644 --- a/contributors/guide/README.md +++ b/contributors/guide/README.md @@ -138,8 +138,8 @@ Follow the link in the SIG name column to reach each SIGs README. Most SIGs will have a set of GitHub Teams with tags that can be mentioned in a comment on issues and pull requests for higher visibility. If you are not sure about the correct SIG for an issue, you can try SIG-contributor-experience [here](/sig-contributor-experience#github-teams), or [ask in Slack](http://slack.k8s.io/). -##### SIG-specific contributing guidelines -Some SIGs also have their own `CONTRIBUTING.md` files, which may contain extra information or guidelines in addition to these general ones. +### SIG-specific contributing guidelines +Some SIGs have their own `CONTRIBUTING.md` files, which may contain extra information or guidelines in addition to these general ones. These are located in the SIG-specific community directories: - [`/sig-apps/CONTRIBUTING.md`](/sig-apps/CONTRIBUTING.md) - [`/sig-aws/CONTRIBUTING.md`](/sig-aws/CONTRIBUTING.md) |