Fix configuration and OpenAPI schema links

docs-main/global-synchronizer/reference/canton-configuration-guide.mdx

@@ -32,12 +32,12 @@ A sample configuration file for two participant nodes and a single synchronizer
 
 ## Configuration reference
 
-The Canton configuration file for static properties is based on [PureConfig](https://pureconfig.github.io/). PureConfig maps Scala case classes and their class structure into analogue configuration options (see e.g. the [PureConfig quick start](https://pureconfig.github.io/docs/#quick-start) for an example). Therefore, the ultimate source of truth for all available configuration options and the configuration file syntax is given by the [CantonConfig Scala reference](/reference/scala/com-digitalasset-canton-config/cantonconfig) and the related types in `com.digitalasset.canton.config`.
+The Canton configuration file for static properties is based on [PureConfig](https://pureconfig.github.io/). PureConfig maps Scala case classes and their class structure into analogue configuration options (see e.g. the [PureConfig quick start](https://pureconfig.github.io/docs/#quick-start) for an example). For the supported configuration options and syntax, see the [Canton configuration reference](/global-synchronizer/reference/configuration-reference).
 
 When understanding the mapping from scaladocs to configuration, please keep in mind that:
 
 - CamelCase Scala names are mapped to lowercase-with-dashes names in configuration files, e.g. `synchronizerParameters` in the scaladocs becomes `synchronizer-parameters` in a configuration file (dash, not underscore).
-- `Option[<scala-class>]` means that the configuration can be specified but doesn't need to be, e.g. you can specify a JWT token via `token=token` in [RemoteParticipantConfig](/reference/scala/com-digitalasset-canton-participant-config/remoteparticipantconfig), but not specifying `token` is also valid.
+- `Option[<scala-class>]` means that the configuration can be specified but doesn't need to be. For example, a JWT token can be specified via `token=token`, but not specifying `token` is also valid.
 
 ## Configuration Compatibility
 

docs-main/openapi/splice/validator/ans-external.yaml

@@ -72,7 +72,7 @@ components:
   securitySchemes:
     userAuth:
       description: |
-        JWT token as described in [spliceAppBearerAuth](../../../../common/src/main/openapi/common-external.yaml#/components/securitySchemes/spliceAppBearerAuth).
+        JWT token using the `spliceAppBearerAuth` security scheme.
         The subject of the token must be ledger API user of the user affected by the endpoint.
       type: http
       scheme: bearer

docs-main/openapi/splice/validator/validator-internal.yaml

@@ -525,14 +525,14 @@ components:
   securitySchemes:
     userAuth:
       description: |
-        JWT token as described in [spliceAppBearerAuth](../../../../common/src/main/openapi/common-external.yaml#/components/securitySchemes/spliceAppBearerAuth).
+        JWT token using the `spliceAppBearerAuth` security scheme.
         The subject of the token must be ledger API user of the user affected by the endpoint.
       type: http
       scheme: bearer
       bearerFormat: JWT
     adminAuth:
       description: |
-        JWT token as described in [spliceAppBearerAuth](../../../../common/src/main/openapi/common-external.yaml#/components/securitySchemes/spliceAppBearerAuth).
+        JWT token using the `spliceAppBearerAuth` security scheme.
         The subject of the token must be ledger API user of the validator operator.
       type: http
       scheme: bearer

docs-main/openapi/splice/validator/wallet-external.yaml

@@ -200,7 +200,7 @@ components:
   securitySchemes:
     walletUserAuth:
       description: |
-        JWT token as described in [spliceAppBearerAuth]("../../../../common/src/main/openapi/common-external.yaml#/components/securitySchemes/spliceAppBearerAuth").
+        JWT token using the `spliceAppBearerAuth` security scheme.
         The subject of the token must be ledger API user of the user whose wallet the endpoint affects.
       type: http
       scheme: bearer