Update Resource Groups docs for the redesigned UI

docs/hub/enterprise-resource-groups.md

@@ -9,12 +9,12 @@ Resource Groups allow organizations to enforce fine-grained access control to th
   <img
     class="block dark:hidden m-0!"
     src="https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/enterprise/resource-groups.png"
-    alt="screenshot of Hugging Face Resource Groups feature"
+    alt="The Overview tab of a resource group"
   />
   <img
     class="hidden dark:block m-0!"
     src="https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/enterprise/dark-resource-groups.png"
-    alt="screenshot of Hugging Face Resource Groups feature"
+    alt="The Overview tab of a resource group"
   />
 </div>
 

docs/hub/jobs-pricing.md

@@ -92,12 +92,12 @@ In this case the Job runs under the organization account, and you can see it in
 If your organization has [Resource Groups](./security-resource-groups) set up, you can attribute job costs to a specific resource group. To do so:
 
 1. You must be a member of the resource group.
-2. Pass the resource group's ID as the `namespace` when running the job.
+2. Pass the resource group's ID as the `resourceGroupId` field when running the job. The `namespace` stays your organization's name, it identifies who is billed.
 
 You can find the resource group's ID in your organization's Resource Groups settings page.
 
 ```bash
-hf jobs run --namespace <resource-group-id> ...
+hf jobs run --namespace <org-name> --resource-group-id <resource-group-id> ...
 ```
 
 In Python:
@@ -107,7 +107,8 @@ In Python:
 >>> run_job(
 ...     image="python:3.12",
 ...     command=["python", "-c", "print('Hello!')"],
-...     namespace="<resource-group-id>",
+...     namespace="<org-name>",
+...     resource_group_id="<resource-group-id>",
 ... )
 ```