en/publishers/permissions.md

@@ -9,18 +9,16 @@ As a basic rule of thumb: A **public** project can be seen by every user of the
 ### Default access rules
 
 We maintain two standard groups:
+
 - **teacher**: This group contains all users, which have been verified as a teacher for computer science, or belongs to the CodeAbility project staff
 - **unauthorizedTeacher**: This group contains users, that claim to be teacher, however we were not able to verify this.
 
-It is up to each project partner to set default access rights for his main group. At the University of Innsbruck, we give on the uppermost level guest access to all teachers:
-![image](uploads/10ae908b065cc69d5c22adf7e2c7ae51/image.png)
-and maintenance rights to all local project members:
-![image](uploads/3022c0da0d341e706bf957f34317138e/image.png)
-Since access rights cannot be withdrawn on lower levels, please get in touch with your local gitlab maintainer for an appropriate solution.
+It is up to each project partner to set default access rights for his main group. At the University of Innsbruck, we give on the uppermost level guest access to all teachers: ![image](uploads/10ae908b065cc69d5c22adf7e2c7ae51/image.png) and maintenance rights to all local project members: ![image](uploads/3022c0da0d341e706bf957f34317138e/image.png) Since access rights cannot be withdrawn on lower levels, please get in touch with your local gitlab maintainer for an appropriate solution.
 
 ### Enforce Public Visibility for Private Projects
 
-Quite often it is the case, that you want to make your project publicly visibile, but want to make the included solution only to a limited audience. To this end you can provide a special entry _publicVisibility:_ in your metadata file, that lists specific exceptions that should not be disclosed to the public. E.g.
+Quite often it is the case, that you want to make most of the content of your project publicly visibile, but want to make the included sample solution only available to a limited audience. To this end you can provide a special entry _publicVisibility_ in your metadata file, that lists specific exceptions that should not be disclosed to the public. E.g.
+
 ```yaml
 ...
 publicVisibility:
@@ -28,4 +26,5 @@ publicVisibility:
         - "solution"
 ...
 ```
+
 will make all files available with the exception of all files and folders that start with {solution}.
\ No newline at end of file