[doc] Update email for feedback on cert-sensitive RFC proposals
Also tweak the phrasing slightly.
diff --git a/doc/project/rfc_process.md b/doc/project/rfc_process.md
index 468b2e9..d5ca0b1 100644
--- a/doc/project/rfc_process.md
+++ b/doc/project/rfc_process.md
@@ -20,7 +20,7 @@
The TC will maintain examples of high quality RFCs to refer to in terms of structure and approach.
* The RFC authors may solicit early feedback while preparing an RFC, possibly before sharing publicly.
* If requested, the TC could help to nominate a small group to shepherd the RFC.
-* If the RFC may contain certification sensitive material (guidance to be shared), it should be first sent to cert-sensitive-priv@lowrisc.org for clearance before sharing more widely.
+* If the RFC potentially contains information that could be certification-sensitive (guidance to be shared), send a note to security@opentitan.org first for feedback.
* The RFC is shared publicly by filing a GitHub issue and tagging with the `Type:RFC` label.
* Once the author is happy that the RFC is complete, they submit it to the Technical Committee for review by adding the label `For TC Review`.
* The Technical Committee will consider active RFCs in each meeting (those that have been marked ready for at least a week).
diff --git a/doc/ug/getting_started_design.md b/doc/ug/getting_started_design.md
index 70d2732..baae77f 100644
--- a/doc/ug/getting_started_design.md
+++ b/doc/ug/getting_started_design.md
@@ -30,9 +30,7 @@
Ideally this proposal document would be created in the Team Drive, but if the author does not have access to the team drive, they can share a privately-created document.
Design proposals should follow the recommended [RFC (Request for Comment)]({{< relref "../project/rfc_process.md" >}}) process, which handles all such proposals.
-If the RFC may contain certification sensitive material (guidance to be shared), it should be first sent to
-[cert-sensitive-priv@lowrisc.org](mailto:cert-sensitive-priv@lowrisc.org)
-for clearance before sharing more widely.
+If the RFC potentially contains information that could be certification-sensitive (guidance to be shared), send a note to security@opentitan.org first for feedback.
The OpenTitan Technical Committee may be able to suggest other collaborators to help with early stage review.
An example of a canonical RFC can be found *here* (TODO).
