code styling and suggestions

Author: petschki

docs/backend/fields.md

@@ -148,22 +148,20 @@ With `plone.autoform` and `plone.supermodel` we can use directives to add inform
 By default, fields are included in the form regardless of the user's permissions.
 Fields can be protected using the `read_permission` and `write_permission` directives.
 The read permission is checked when the field is in display mode, and the write permission is checked when the field is in input mode.
-The permission should be given with its Zope 3-style name (i.e. cmf.ManagePortal rather than 'Manage portal').
+The permission should be given with its Zope 3-style name (such as `cmf.ManagePortal` instead of `Manage portal`).
 
-In this example, the `secret` field is protected by the
-`cmf.ManagePortal` permission as both a read and write permission.
-This means that in both display and input modes, the field will
-only be included in the form for users who have that permission:
+In this example, the `secret` field is protected by the `cmf.ManagePortal` permission as both a read and write permission.
+This means that in both display and input modes, the field will only be included in the form for users who have that permission:
 
 ```python
 from plone.supermodel import model
 from plone.autoform import directives as form
 
 class IMySchema(model.Schema):
-    form.read_permission(secret='cmf.ManagePortal')
-    form.write_permission(secret='cmf.ManagePortal')
+    form.read_permission(secret="cmf.ManagePortal")
+    form.write_permission(secret="cmf.ManagePortal")
     secret = schema.TextLine(
-        title = u'Secret',
+        title = u"Secret",
         )
 ```
 

docs/backend/schemas.md

@@ -224,10 +224,10 @@ Note this won't have behavior fields added to it at this stage, only the fields
 With `plone.autoform` and `plone.supermodel` we can use directives to add information to the schema fields.
 
 
-### Omitting fields
+### Omit fields
 
 A field can be omitted entirely from all forms, or from some forms, using the `omitted` and `no_omit` directives.
-In this example, the `dummy` field is omitted from all forms, and the `edit_only` field is omitted from all forms except those that provide the IEditForm interface:
+In this example, the `dummy` field is omitted from all forms, and the `edit_only` field is omitted from all forms except those that provide the `IEditForm` interface:
 
 ```{code-block} python
 :emphasize-lines: 7,12,13
@@ -239,15 +239,15 @@ from plone.autoform import directives as form
 
 class IMySchema(model.Schema):
 
-    form.omitted('dummy')
+    form.omitted("dummy")
     dummy = schema.Text(
         title=u"Dummy"
         )
 
-    form.omitted('edit_only')
-    form.no_omit(IEditForm, 'edit_only')
+    form.omitted("edit_only")
+    form.no_omit(IEditForm, "edit_only")
     edit_only = schema.TextLine(
-        title = u'Only included on edit forms',
+        title = u"Only included on edit forms",
         )
 ```
 
@@ -272,7 +272,7 @@ In supermodel XML, this can be specified as:
 `form:omitted` may be either a single boolean value, or a space-separated list of form_interface:boolean pairs.
 
 
-### Re-ordering fields
+### Reorder fields
 
 A field's position in the form can be influenced using the `order_before` and `order_after` directives.
 In this example, the `not_last` field is placed before the `summary` field even though it is defined afterward:
@@ -292,15 +292,15 @@ class IMySchema(model.Schema):
         readonly=True
         )
 
-    form.order_before(not_last='summary')
+    form.order_before(not_last="summary")
     not_last = schema.TextLine(
         title=u"Not last",
         )
 ```
 
-The value passed to the directive may be either '*' (indicating before or after all fields) or the name of another field.
-Use `'.fieldname'` to refer to field in the current schema or a base schema.
-Prefix with the schema name (e.g. `'IDublinCore.title'`) to refer to a field in another schema.
+The value passed to the directive may be either `*` (indicating before or after all fields) or the name of another field.
+Use `.fieldname` to refer to field in the current schema or a base schema.
+Prefix with the schema name (e.g. `IDublinCore.title`) to refer to a field in another schema.
 Use an unprefixed name to refer to a field in the current or the default schema for the form.
 
 In supermodel XML, the directives are called `form:before` and `form:after`.
@@ -345,7 +345,7 @@ class IMySchema(model.Schema):
         )
 ```
 
-In supermodel XML fieldsets are specified by grouping fields within a `<fieldset>` tag:
+In supermodel XML, fieldsets are specified by grouping fields within a `<fieldset>` tag:
 
 ```xml
 <fieldset name="extra" label="Extra info">

docs/backend/widgets.md

@@ -65,7 +65,7 @@ The main widgets are:
 
 (backend-widgets-fields-display-label)=
 
-## Changing a field's display mode
+## Change a field's display mode
 
 A field's widget can be displayed in several modes:
 
@@ -91,8 +91,8 @@ from plone.autoform import directives as form
 
 class IMySchema(model.Schema):
 
-    form.mode(secret='hidden')
-    form.mode(IEditForm, secret='input')
+    form.mode(secret="hidden")
+    form.mode(IEditForm, secret="input")
     secret = schema.TextLine(
         title=u"Secret",
         default=u"Secret stuff (except on edit forms)"
@@ -132,7 +132,7 @@ In other words, `form:mode` may be either a single mode, or a space-separated li
 
 (backend-widgets-fields-widget-label)=
 
-## Changing a field's widget
+## Change a field's widget
 
 You can change the widget that you use for a field in several ways.
 This section describes these methods.

docs/classic-ui/forms.md

@@ -131,9 +131,15 @@ See the corresponding chapters to learn how to control field and widget presenta
 
 ```{seealso}
 {ref}`Field permission <backend-fields-schema-label>`
+```
+```{seealso}
 {ref}`Ordering, omitting, grouping <backend-schemas-directives-label>`
-{ref}`Changing a field's display mode <backend-widgets-fields-display-label)>`
-{ref}`Changing a field's widget <backend-widgets-fields-widget-label)>`
+```
+```{seealso}
+{ref}`Changing a field's display mode <backend-widgets-fields-display-label>`
+```
+```{seealso}
+{ref}`Changing a field's widget <backend-widgets-fields-widget-label>`
 ```