From 3a7a1ff2180b7dc4633e858ac43b5766674e4db3 Mon Sep 17 00:00:00 2001
From: "copybara-service[bot]" <copybara-service[bot]@users.noreply.github.com>
Date: Mon, 26 Aug 2024 18:47:54 +0000
Subject: [PATCH] Latest docs on successful build 6613 auto-pushed to gh-pages

---
 api/latest/com/google/errorprone/annotations/ThreadSafe.html | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/api/latest/com/google/errorprone/annotations/ThreadSafe.html b/api/latest/com/google/errorprone/annotations/ThreadSafe.html
index a84fda62566..9b9e32f46e1 100644
--- a/api/latest/com/google/errorprone/annotations/ThreadSafe.html
+++ b/api/latest/com/google/errorprone/annotations/ThreadSafe.html
@@ -135,7 +135,10 @@ <h1 title="Annotation Type ThreadSafe" class="title">Annotation Type ThreadSafe<
    <li>it is annotated with <a href="ThreadSafe.html" title="annotation in com.google.errorprone.annotations"><code>ThreadSafe</code></a>.
  </ul>
 
- <p>This first requirement means the type is at least inherently shallowly thread-safe.
+ <p>This first requirement means the type is at least inherently shallowly thread-safe. For types
+ with type parameters to be deemed deeply thread-safe, those of these types that denote
+ containment must also be deemed thread-safe. A full explanation of this can be found in the
+ <a href="ThreadSafeTypeParameter.html" title="annotation in com.google.errorprone.annotations"><code>ThreadSafeTypeParameter</code></a> javadoc.
 
  <p>Fields annotated with <code>javax.annotation.concurrent.GuardedBy</code> are likely the meat of a
  mutable thread-safe class: these are things that need to be mutated, but should be done so in a