From 9b31e9f82fe059ad1776676082de8d098a1ab4b4 Mon Sep 17 00:00:00 2001
From: florian <f.spreckelsen@inidscale.com>
Date: Fri, 5 Aug 2022 14:34:49 +0200
Subject: [PATCH] FIX: Typos
---
src/doc/gallery/curator-permissions.rst | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/src/doc/gallery/curator-permissions.rst b/src/doc/gallery/curator-permissions.rst
index 9f1b3259..e486f9aa 100644
--- a/src/doc/gallery/curator-permissions.rst
+++ b/src/doc/gallery/curator-permissions.rst
@@ -2,10 +2,10 @@
Setting permissions for a curator role
======================================
-The following example shows how to creaate and set permissions for a ``curator``
+The following example shows how to create and set permissions for a ``curator``
role that is allowed to insert, update, or delete any entity apart from a set of
RecordTypes and properties that define a "core data model" which can only be
-altered whith administration permissions.
+altered with administration permissions.
In the following, you'll learn how to
@@ -43,7 +43,7 @@ this role. Assume you already have created and activated (see
.. note::
- The ``test_curator`` user shouldn't have administration priveleges, otherwise
+ The ``test_curator`` user shouldn't have administration privileges, otherwise
the below changes won't have any effect.
The core data model and caosdb-advanced-user-tools
@@ -55,7 +55,7 @@ or yaml file (just adapt lines 39-42 accordingly). In this example, we'll use th
developed b J. Schmidt at the `Leibniz Centre for Tropical Marine Research
<https://www.leibniz-zmt.de/en/>`_.
-Clone the schemas into the same directory containing the below script via
+Clone the schemata into the same directory containing the below script via
.. code:: console
@@ -63,7 +63,7 @@ Clone the schemas into the same directory containing the below script via
Furthermore, we'll need the `CaosDB Advanced User Tools
<https://gitlab.com/caosdb/caosdb-advanced-user-tools>`_ for loading the
-metadata schemas from the json files, so install them via
+metadata schemata from the json files, so install them via
.. code:: console
@@ -87,7 +87,7 @@ This means that, by default, all users with the ``curator`` role are **granted**
all entity permissions (including insert, update, and delete as specified in the
beginning) **with priority**. This ensures, that no normal user is allowed to
overrule these permissions (since it is granted with priority), but it can still
-be denied for the core data model entities by a **deny** rule with prioirty. See
+be denied for the core data model entities by a **deny** rule with priority. See
the server documentation on `permission
calculation <https://docs.indiscale.com/caosdb-server/permissions.html#permission-calculation>`_
for more information on which permission rules can or can't be overruled.
--
GitLab