Internal change

PiperOrigin-RevId: 291457092

LICENSE

@@ -224,7 +224,7 @@ subject to and limited by the following restrictions:
 UNLESS OTHERWISE MUTUALLY AGREED TO BY THE PARTIES IN WRITING, LICENSOR
 OFFERS THE WORK AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY
 KIND CONCERNING THE WORK, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE,
-INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITechnical LeadE, MERCHANTIBILITY,
+INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTIBILITY,
 FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, OR THE ABSENCE OF
 LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OF ABSENCE OF ERRORS,
 WHETHER OR NOT DISCOVERABLE. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION

review/reviewer/standard.md

@@ -104,7 +104,7 @@ the CL, for future readers.)
 
 If that doesn't resolve the situation, the most common way to resolve it would
 be to escalate. Often the
-escalation path is to a broader team discussion, having a Technical Lead weigh in, asking
+escalation path is to a broader team discussion, having aTechnical Leadweigh in, asking
 for a decision from a maintainer of the code, or asking an Eng Manager to help
 out. **Don't let a CL sit around because the author and the reviewer can't come
 to an agreement.**