diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-06-11 11:42:31 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-06-11 11:42:31 -0700 |
| commit | 91bba5d0aeeffe12a3312ca6df017ab581e28144 (patch) | |
| tree | 3df797af943a2c613f09db1bc67dfdf3be67b0ff | |
| parent | 2b010899411d5bee6ca0fdf621d6ace1bfaf8782 (diff) | |
| parent | a803f895b06f330967769637c5276b8664b16d23 (diff) | |
Merge pull request #2242 from mirake/fix-typos
Typo fix: subcribe -> subscribe
| -rw-r--r-- | sig-governance.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sig-governance.md b/sig-governance.md index 254dab69..96194359 100644 --- a/sig-governance.md +++ b/sig-governance.md @@ -37,7 +37,7 @@ In order to standardize Special Interest Group efforts, create maximum transpare 5. Share individual events with `cgnt364vd8s86hr2phapfjc6uk@group.calendar.google.com` to publish on the universal calendar. * Use existing proposal and PR process (to be documented) * Announce new SIG on kubernetes-dev@googlegroups.com -* Leads should [subcribe to the kubernetes-sig-leads mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-leads) +* Leads should [subscribe to the kubernetes-sig-leads mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-leads) * Submit a PR to add a row for the SIG to the table in the kubernetes/community README.md file, to create a kubernetes/community directory, and to add any SIG-related docs, schedules, roadmaps, etc. to your new kubernetes/community/SIG-foo directory. ### **Creating service accounts for the SIG** |