From b6273fbec1ea221510748cf25d31263f5f4b5372 Mon Sep 17 00:00:00 2001 From: Julien Chaumond Date: Tue, 17 Dec 2024 14:46:33 +0100 Subject: [PATCH] [gating group collections] micro tweaks --- docs/hub/enterprise-hub-gating-group-collections.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/hub/enterprise-hub-gating-group-collections.md b/docs/hub/enterprise-hub-gating-group-collections.md index 7c2749eb6..f6b2b9d7e 100644 --- a/docs/hub/enterprise-hub-gating-group-collections.md +++ b/docs/hub/enterprise-hub-gating-group-collections.md @@ -11,7 +11,7 @@ To enable Gating Group in a collection: - the collection owner must be an organization - the organization must be subscribed to the Enterprise Hub - all models and datasets in the collection must be owned by the same organization as the collection -- each model or dataset in the collection may only belong to one Gating Group Collection, but they may be present on non-gating collections. +- each model or dataset in the collection may only belong to one Gating Group Collection (but they can still be included in non-gating i.e. _regular_ collections). Gating only applies to models and datasets; any other resource part of the collection (such as a Space or a Paper) won't be affected. @@ -146,7 +146,7 @@ There is currently no way to customize the gate parameters and requested informa ## Access gated repos in a Gating Group Collection as a user -A Gated Group Collection shows a specific icon before its name: +A Gated Group Collection shows a specific icon next to its name: