update release team roles

- Testing -> CI Signal
- {Automatic, Manual} Upgrade Testing Lead  -> Upgrade Testing Lead

sig-release/README.md

@@ -16,17 +16,16 @@
  - [Features Lead](#features-lead)
  - [Bug Triage Lead](#bug-triage-lead)
  - [Test Infra Lead](#test-infra-lead)
- - [Automated Upgrade Testing Lead](#automated-upgrade-testing-lead)
- - [Manual Upgrade Testing Lead](#manual-upgrade-testing-lead)
- - [Testing Lead](#testing-lead)
+ - [Upgrade Testing Lead](#upgrade-testing-lead)
+ - [CI Signal Lead](#ci-signal-lead)
  - [Release Team Shadow](#release-team-shadow)
  - [Individual Contributors](#individual-contributors)
  - [During a patch pelease](#during-a-patch-pelease)
  - [During a major/minor release](#during-a-majorminor-release)
- - [Propose and Track Feature](#propose-and-track-feature)
- - [Write Feature Documentation](#write-feature-documentation)
+ - [Propose and track feature](#propose-and-track-feature)
+ - [Write feature documentation](#write-feature-documentation)
 - [Other activities of the Release Team](#other-activities-of-the-release-team)
- - [During "Major" Releases](#during-major-releases)
+ - [During "Major" releases](#during-major-releases)
  - [During "Security" releases](#during-security-releases)
 - [References](#references)
 
@@ -192,16 +191,14 @@ be familiar with the release process and remain ready to discharge the responsib
 ### Test Infra Lead
 - Sets up and maintains all CI for the release branch
 
-### Automated Upgrade Testing Lead
+### Upgrade Testing Lead
 - Ensures that automated upgrade tests provide a clear go/no-go signal for the release
 - Tracks and finds owners for all issues with automated upgrade tests
-
-### Manual Upgrade Testing Lead
 - Ensures that any gaps in automated upgrade testing are covered by manual upgrade testing
 - Organizes the manual upgrade testing efforts, including setting up instructions for manual testing,
  finding manual testing volunteers, and ensuring any issues discovered are communicated widely and fixed quickly
 
-### Testing Lead
+### CI Signal Lead
 - Ensures that all non-upgrade test CI provides a clear go/no-go signal for the release
 - Tracks and finds owners to fix any issues with any (non-upgrade) tests
 
@@ -222,14 +219,14 @@ If you have a patch that needs to be ported back to a previous release (meaning
 
 #### During a major/minor release
 
-##### Propose and Track Feature
+##### Propose and track feature
 If you are developing a feature for Kubernetes, make sure that an issue is open in the [features repository](https://github.com/kubernetes/features/issues). If you are targeting a particular release, make sure the issue is marked with the corresponding release milestone.
 
 Ensure that all code for your feature is written, tested, reviewed, and merged before code freeze date for the target release.
 
 During the code freeze period, fix any bugs discovered with you feature, and write feature documentation.
 
-##### Write Feature Documentation
+##### Write feature documentation
 
 1. Make sure your feature for the upcoming release is on the release tracking board (e.g. [link](https://docs.google.com/spreadsheets/d/1nspIeRVNjAQHRslHQD1-6gPv99OcYZLMezrBe3Pfhhg/edit#gid=0) for 1.6).
 2. Create a PR with documentation for your feature in the [documents repo](https://github.com/kubernetes/kubernetes.github.io).
@@ -242,7 +239,7 @@ During the code freeze period, fix any bugs discovered with you feature, and wri
 
 ## Other activities of the Release Team
 
-### During "Major" Releases
+### During "Major" releases
 To date no major release has been scheduled, however, SIG Release would be responsible for working closely with SIG PM
 and SIG Testing to coordinate this effort across SIGs. The precise work required to produce a major relaese (e.g. 2.0, 3.0)
 is undefined.