Tidy misc.md

Author: stevepiercy

plone.app.dexterity/reference/misc.md

@@ -1,30 +1,26 @@
 ---
 myst:
   html_meta:
-    "description": ""
-    "property=og:description": ""
-    "property=og:title": ""
-    "keywords": ""
+    "description": "Miscellaneous contributor contributed recipes for content types and schema in Plone"
+    "property=og:description": "Miscellaneous contributor contributed recipes for content types and schema in Plone"
+    "property=og:title": "Miscellaneous contributor contributed recipes for content types and schema in Plone"
+    "keywords": "Plone, miscellaneous, recipes, content types"
 ---
 
-# Miscellaneous
+# Miscellaneous recipes
 
-## User contributed recipes
+## Hiding a field
 
-**How to hide a field on a schema if we do not want to or cannot modify the original schema**
-
-To do this one can use tagged values on the schema. In this case want to hide 'introduction' and 'answers' fields:
+On occasion you may want to hide a field in a schema without modifying the original schema.
+To do this, you can use tagged values on the schema.
+In this example, you would hide the `introduction` and `answers` fields:
 
 ```python
 from example.package.content.assessmentitem import IAssessmentItem
 from plone.autoform.interfaces import OMITTED_KEY
 IAssessmentItem.setTaggedValue(OMITTED_KEY,
-                           [(Interface, 'introduction', 'true'),
-                            (Interface, 'answers', 'true')])
+                           [(Interface, "introduction", "true"),
+                            (Interface, "answers", "true")])
 ```
 
-This code can sit in another.package.\_\_init\_\_.py for example.
-
-See also: [Original thread on coredev mailinglist]
-
-[original thread on coredev mailinglist]: http://plone.293351.n2.nabble.com/plone-autoform-why-use-tagged-values-td7560956.html
+This code can reside in {file}`another.package.__init__.py`.