Merge branch 'main' into t1

content/actions/security-guides/encrypted-secrets.md

@@ -213,7 +213,15 @@ You can check which access policies are being applied to a secret in your organi
 
 {% note %}
 
-**Note:** {% data reusables.actions.forked-secrets %}
+**Notes:**
+
+* {% data reusables.actions.forked-secrets %}
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
+
+* Secrets are not automatically passed to reusable workflows. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows#passing-inputs-and-secrets-to-a-reusable-workflow)."
+
+{% endif %}
 
 {% endnote %}
 

data/reusables/organizations/types-of-team-visibility.md

@@ -2,3 +2,5 @@ Teams can be visible or secret:
 
 - Visible teams can be [viewed and @mentioned](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) by every organization member.
 - Secret teams are only visible to the people on the team and people with owner permissions. They're great for hiding teams with sensitive names or members, such as those used for working with external partners or clients. Secret teams cannot be nested under parent teams or have child teams.
+
+People who are not members of the organization cannot view any teams.