diff --git a/pandora/config.pandora.jsonc b/pandora/config.pandora.jsonc
index 93cc454b8..2e19f2440 100644
--- a/pandora/config.pandora.jsonc
+++ b/pandora/config.pandora.jsonc
@@ -98,7 +98,7 @@ examples (config.SITENAME.jsonc) that are part of this pan.do/ra distribution.
     with "name", "biography", "photo" etc). The HTML representation for
     entities can be customized by adding "/static/js/entity.SITENAME.js".
     Each entity has the following properties:
-        "id": Internal ID (can be referenced in "layers")
+        "id": Unique internal ID (can be referenced in "layers")
         "title": Human-readable title
         "keys": List of properties
         "sortType": Optional. If set to "person" or "title", then the sort
@@ -106,7 +106,7 @@ examples (config.SITENAME.jsonc) that are part of this pan.do/ra distribution.
     Each key has the properties "id", "title" and "type". "type" can be
     "boolean", "number", "string", "text", "document" (reference to the id of a
     document added via "Manage Documents") or ["string"] (list of strings).
-    "id" and "name" keys are required. If "additional_names" is present, these
+    "id" and "name" keys are required. If "additionalNames" is present, these
     will act as synonyms when autocompleting values entered as annotations.
     */
     "entities": [],
@@ -143,7 +143,7 @@ examples (config.SITENAME.jsonc) that are part of this pan.do/ra distribution.
     are "*", "id" and "title". Adding a key with "random" as id will produce a
     random value; this can be used for a "random" sort order.
     An itemKey must have the following properties:
-        "id": The id of the key (as known by the server)
+        "id": The unique id of the key (as known by the server)
         "title": The title of the key (as displayed by the client)
         "type": Can be "boolean", "date", "enum", "float", "hue", "integer",
             "layer", "string", "text", "time" or ["..."] (list of values of
@@ -552,7 +552,7 @@ examples (config.SITENAME.jsonc) that are part of this pan.do/ra distribution.
         "type": Can be "entity", "string" or "text" (strings cannot contain
             line breaks, text can contain HTML markup).
     Optional keys are:
-        "canAddAnnotations":
+        "canAddAnnotations": Permissions per user level
         "entity": ID of the referenced entity (if type is "entity")
         "hasEvents": If true, the calendar will be populated with matches from
             this layer