fix up markdown docs conversion issues

- introduced in #8759 & #8569

docs/advanced_topics/api/v2/configuration.md

@@ -40,11 +40,9 @@ can hook into the rest of your project.
 
 Wagtail provides three endpoint classes you can use:
 
-```{eval-rst}
-- Pages :class:`wagtail.api.v2.views.PagesAPIViewSet`
-- Images :class:`wagtail.images.api.v2.views.ImagesAPIViewSet`
-- Documents :class:`wagtail.documents.api.v2.views.DocumentsAPIViewSet`
-```
+-   Pages {class}`wagtail.api.v2.views.PagesAPIViewSet`
+-   Images {class}`wagtail.images.api.v2.views.ImagesAPIViewSet`
+-   Documents {class}`wagtail.documents.api.v2.views.DocumentsAPIViewSet`
 
 You can subclass any of these endpoint classes to customize their functionality.
 Additionally, there is a base endpoint class you can use for adding different

docs/reference/hooks.md

@@ -137,7 +137,7 @@ def add_another_welcome_panel(request, panels):
 
 ### `construct_homepage_summary_items`
 
-Add or remove items from the 'site summary' bar on the admin homepage (which shows the number of pages and other object that exist on the site). The callable passed into this hook should take a `request` object and a list of summary item objects, and should modify this list in-place as required. Summary item objects are instances of `wagtail.admin.site_summary.SummaryItem`, which extends :ref:`the Component class <creating_template_components>` with the following additional methods and properties:
+Add or remove items from the 'site summary' bar on the admin homepage (which shows the number of pages and other object that exist on the site). The callable passed into this hook should take a `request` object and a list of summary item objects, and should modify this list in-place as required. Summary item objects are instances of `wagtail.admin.site_summary.SummaryItem`, which extends [the Component class](creating_template_components) with the following additional methods and properties:
 
 ```{eval-rst}
   .. method:: SummaryItem(request)

docs/topics/writing_templates.md

@@ -35,7 +35,7 @@ For more information, see the Django documentation for the [application director
 
 The data/content entered into each page is accessed/output through Django's `{{ double-brace }}` notation. Each field from the model must be accessed by prefixing `page.`. e.g the page title `{{ page.title }}` or another field `{{ page.author }}`.
 
-A custom variable name can be :attr:`configured on the page model <wagtail.models.Page.context_object_name>`. If a custom name is defined, `page` is still available for use in shared templates.
+A custom variable name can be configured on the page model {attr}`wagtail.models.Page.context_object_name`. If a custom name is defined, `page` is still available for use in shared templates.
 
 Additionally `request.` is available and contains Django's request object.