rules,faq: Adjust english wording

faq-en.md

@@ -4,13 +4,13 @@
 Published links become invalid once your account is deleted at the end of your university affiliation. For public repositories a university facility should take responsibility as long as the project is to be publicly available.
 
 ### Is this CIP GitLab the right choice for non-university projects?
-No, most of GitLab's functionality like issues, merge-requests, etc. are only made available to university members. External accounts are only created for good reasons. That might be something like extensive collaboration at a university related project, not just simple bug reports or merge-requests.
+No, most of GitLab's functionality like issues, merge-requests, etc. are only available to university members. External accounts are only created for good reasons. That might be something like extensive collaboration at a university related project, not just simple bug reports or merge-requests.
 
 ### What about backups?
-Yes, there are daily backups. Git repositories can easily be restored, however, GitLab's backup does not offer restoration of individual projects (incl. its issues, merge-requests, see [here](https://gitlab.com/gitlab-org/gitlab-ce/issues/2397)).
+Yes, there are daily backups. Git repositories can easily be restored, however, GitLab's backup does not offer restoration of individual projects incl. its issues, merge-requests (see [here](https://gitlab.com/gitlab-org/gitlab-ce/issues/2397)).
 
 ### Continuous Integration?
-We maintain a shared runner for all of our users. Be reasonable with your resource usage. You can also integrate your own runners.
+We maintain a shared runner for all of our users. Be mindful of reasonable resource usage. You can also integrate your own runners.
 
 ### Problems?
 [problems@cip.cs.fau.de](mailto:problems@cip.cs.fau.de)

rules-en.md

@@ -7,22 +7,22 @@
 
 ### Repositories
 
-   * For development of source code files (program code, TeX code, .txt files, etc.) only.
-   * Binary files are to be avoided as far as possible, no collections of images, videos, PDF files, Word documents, archive files, etc. in particular.
-   * Owners of repositories that are too large are automatically requested to reduce their memory usage to a reasonable level.
-   * Repositories are deleted as soon as all of their owners have been deleted.
+   * Only for development of source code files (program code, TeX code, .txt files, etc.).
+   * Binary files are to be avoided wherever possible. In particular no collections of images, videos, PDF files, Word documents, archive files, etc.
+   * Owners of overly large repositories are automatically requested to be mindful of reasonable disk usage.
+   * Repositories are deleted once all of their owners have been deleted.
    * Repositories should only be published by chairs, university groups, university facilities (see FAQ).
 
 ### Groups
 
    * Group names must not look like IDM identifiers (e.g. ab12cdef, siabcdef, snasdfoo, unrz123).
    * Group names must not be in conflict with names of lectures, university facilities, etc.
-   * Groups will be deleted as soon as all of their owners have been deleted.
+   * Groups will be deleted once all of their owners have been deleted.
 
 ### Continuous Integration
 
-   * Be reasonable with the disk usage of your build artifacts.
-   * Build artifacts must not be stored forever.
+   * Be mindful of reasonable disk usage for build artifacts.
+   * Build artifacts must not be stored permanently.
 
 ### Misc