Doc changes

Author: Ruin0x11

org-jira.el

@@ -333,11 +333,11 @@ See `org-default-priority' for more info."
   "An alist of plists containing custom fields to add to issues.
 
 A sample value might be
-  ((customfield_10033 . (:type string :location 'headline))
-   (customfield_10108 . (:type number :location 'property :name \"Priority\"))).
+  '((customfield_10033 . (:type string :location 'headline))
+    (customfield_10108 . (:type number :location 'property :name \"Priority\"))).
 
 List of properties for each plist:
-    :type - Required. Type of the field. Defaults are 'string, 'boolean or
+    :type - Type of the field (required). Built-in types are 'string, 'boolean or
             'number. You can define custom types inside
             `org-jira-custom-field-encoders'.
     :location - A symbol, either 'property to format the field as an Org
@@ -354,7 +354,7 @@ List of properties for each plist:
   "An alist of plists containing custom field type handlers.
 
 A sample value might be
-  ((multicheckboxes . (:encode #'my-encoder :decode #'my-decoder)))
+  '((multicheckboxes . (:encode #'my-encoder :decode #'my-decoder)))
 
 Encoding functions take a JSON value and return a string.
 Decoding functions take a string and return a JSON value."
@@ -366,6 +366,9 @@ Decoding functions take a string and return a JSON value."
 The car of each element is the org-jira field name.
 The cdr of each element is the Jira issue field ID as returned by the API.
 
+This is useful if your organization uses a custom field for the
+issue description or other \"built-in\" field instead of the default.
+
 A sample value might be
   '((description . customfield_10000)
     (summary . customfield_10001)
@@ -389,7 +392,6 @@ Valid org-jira fields you can use:
 - status
 - summary
 - issuetype
-- issuetype
 - updated"
   :group 'org-jira
   :type '(alist :key-type symbol :value-type symbol))