Corrected some inaccuracies for Shared resources (Storage and Cloud services)

docs/data_management/storage/cheaha_storage_gpfs/project_directories.md

@@ -132,6 +132,6 @@ This section outlines key storage policies and exceptions, including access cont
 
 - Storage Entitlement: A shared project allocation of 25 TB is available to research labs led by a PI and to Core Facilities headed by a Director. A shared project allocation is intended to support active research and collaboration.
 - Quota Increase: At this time, we do not provide additional quota increase for shared project allocation. If you require more storage for your work, please consider requesting and using an [LTS](../lts/index.md).
-- Data Management: The owner the shared Project allocation is responsible for organizing, cleaning, and backing up their data in their shared Project allocation.
-- Permission and Access Control Management: Access to shared project allocation can be managed using Access Control Lists (ACLs). New members can be added to or removed from the group access based on PI approval.
-- HIPAA Compliance: Shared project allocation is HIPAA compliant and can accept Protected Health Information (PHI) data. For HIPAA Compliance and UAB policies surrounding PHI data, please refer the [HIPAA Compliance](../index.md#hipaa-compliance)page.
+- Data Management: The owner of a shared Project allocation is responsible for organizing, cleaning, and backing up their data in their shared Project allocation.
+- Permission and Access Control Management: Access to shared project allocations is primarily managed through group membership, with users added or removed based on Principal Investigator (PI) approval. Access Control Lists (ACLs) may be used only for exceptions requiring finer control.
+- HIPAA Compliance: Shared project allocation is HIPAA compliant and can store Protected Health Information (PHI) data. For HIPAA Compliance and UAB policies surrounding PHI data, please refer to the [HIPAA Compliance](../index.md#hipaa-compliance) page.

docs/uab_cloud/sharing_cloud_environment.md

@@ -1,10 +1,10 @@
 # What Is a Project Space?
 
-UAB's cloud infrastructure is based on [OpenStack](https://docs.openstack.org/2024.1/) cloud software. A project space is referred to as the cloud environment that houses projects on OpenStack. Providing the platform to manage cloud resources for storage, security and networking via a web interface. Every UAB Cloud user has their Individual Cloud Environment that is their personal project space. An individual can also be part of a shared project space which is referred to as a Shared Cloud Environment. Both environments are OpenStack Project Spaces, with the exception that the shared cloud environment allows multiple UAB cloud users to collaborate in the shared project space. Dependent on an individual's UAB status, they can request that a Shared Cloud environment be created for their Lab and/or Core, this shared project space will include members of their research lab, or persons they want to collaborate with. This article provides information on why using a shared cloud environment is important, how to get an additional shared OpenStack Project (Shared Cloud Environment) and how best to utilize this environment.
+UAB's cloud infrastructure is based on [OpenStack](https://docs.openstack.org/2024.1/). A project space (OpenStack project/tenant) serves as an isolated environment for managing cloud resources, including compute, storage, networking, and security, through a web interface. Every UAB Cloud user is assigned an Individual Cloud Environment, which corresponds to their personal OpenStack project. Users may also be members of a Shared Cloud Environment, which is a shared OpenStack project that enables multiple users to collaborate within the same resource space. As with other Shared Resource allocation a Principal Investigator (PI) or Core Director may request the creation of a Shared Cloud Environment for their lab or core. This shared project space can include members of the research group and other collaborators as needed. This article outlines the benefits of using a Shared Cloud Environment, how to request a Shared Cloud Environment (shared OpenStack project), and good practices for managing and utilizing this environment.
 
 ## Why Do I Need a Shared Cloud Environment
 
-The dedicated Shared Cloud Environment available on UAB Cloud offer research Labs and/or Cores a number of solutions for managing their various and intensive computational needs. These Shared Cloud Environments will provide a secure and collaborative environment where members can access, share, and manage resources efficiently. By using this resource, your organization can ensure that their research projects have the necessary computing power and flexibility to advance scientific inquiry, facilitate collaboration, and optimize resource utilization. The benefits of having a Shared Cloud Environment on UAB Cloud are;
+The dedicated Shared Cloud Environment available on UAB Cloud offer research Labs and/or Cores a number of solutions for managing their various computational needs. These environments will provide a secure and collaborative space where members can access, share, and manage resources efficiently. By using this resource, your organization can ensure that their research projects have the necessary computing power and flexibility to advance scientific discovery, facilitate collaboration, and optimize resource utilization. The benefits of having a Shared Cloud Environment on UAB Cloud are;
 
 1. Improved collaborations between members of your lab, as they all have access to the same resources and data to facilitate research.
 1. Specific environments can be created from Instances that support highly specialized research tools only available on particular OS, and hardware. These specific environments can be created to significantly improve compute times for your research.