tweak release note IQSS#11281

Author: pdurbin

doc/release-notes/11281-ExternalSearch.md

@@ -2,13 +2,15 @@
 
 Dataverse now has an experimental capability to dynamically add and configure new search engines.
 The current Dataverse user interface can be configured to use a specified search engine instead of the built-in solr search.
-The search API now supports an optional &searchService query parameter that allows using any configured search engine.
+The search API now supports an optional `searchService` query parameter that allows using any configured search engine.
 An additional /api/search/services endpoint allows discovery of the services installed.
 
 In addition to two trivial example services designed for testing, Dataverse ships with two search engine classes that support calling an externally-hosted search service (via HTTP GET or POST).
 These classes rely on the internal solr search to perform access-control and to format the final results, simplifying development of such an external engine.
 
-Details about the new functionality are described in https://guides.dataverse.org/en/latest/developers/search-services.html
+Details about the new functionality are described in https://dataverse-guide--11281.org.readthedocs.build/en/11281/developers/search-services.html
+
+See also #11281.
 
 ## Settings
 
@@ -24,4 +26,4 @@ Details about the new functionality are described in https://guides.dataverse.or
 ### New Configuration Options
 
 - `dataverse.search.services.directory`
-- `dataverse.search.default-service`
+- `dataverse.search.default-service`