Update docs/explanations/structuring_your_project.md

Co-authored-by: Brad Macdonald <[email protected]>

docs/explanations/structuring_your_project.md

@@ -11,7 +11,7 @@ We recommend creating Synapse Teams for permission management on your Synapse pr
 * **<project> Admin** - This team should have "Administrator" access to the project and is used to used to manage the project and grant access to other teams.
 * **<project> Users** - This team is optional, but can be used to grant a curated set of users download access to the project, by grant "Can Download" permission to the team. If you want to grant all registered users on Synapse download access to your project, click the "Make Public" button in project's sharing settings instead of creating and managing this team.
 
-Below are some key permission criterias to consider when setting up your project:
+Below are some key permission criteria to consider when setting up your project:
 
 * Create a Synapse Team and Project per data contributor if there are (1) multiple data contributors and (2) the data contributors should not have access to each other's raw data. You would then create a central "public" project that will contain the harmonized data. You can technically leverage [local share settings](https://help.synapse.org/docs/Sharing-Settings,-Permissions,-and-Conditions-for-Use.2024276030.html#SharingSettings,Permissions,andConditionsforUse-EditSharingSettingsonFiles,Folders,andTables) by creating private folders in one project but managing local share settings is more complicated and not recommended.
 * Do not mix data that requires different permission models within a folder. For example, if you have a project that contains both public and private data, you should create two folders, one for public data and one for private data.  You can then grant the appropriate permissions to each folder. You can use local share settings to manage each file's permission, but this is not recommended!