@@ -193,8 +193,8 @@ information.
193
193
194
194
If you want to choose which model resolution strategy is used, you use the `resolveAspectModel()`
195
195
method of the `AspectModelResolver`. In this case, you need to provide the resolution strategy and
196
- and the initial input (`InputStream`, `Model` or a `String` containing RDF/Turtle), or one or more
197
- URNs of model elements to resolve - have a look at the methods provided by `AspectModelResolver`.
196
+ the initial input (`InputStream`, `Model` or a `String` containing RDF/Turtle), or one or more URNs
197
+ of model elements to resolve - have a look at the methods provided by `AspectModelResolver`.
198
198
199
199
++++
200
200
<details>
@@ -305,8 +305,8 @@ include::example$ValidateAspectModel.java[tags=imports]
305
305
include::example$ValidateAspectModel.java[tags=validate]
306
306
----
307
307
308
- <1> For an immediate human-readable result of the validation result , use the `ViolationFormatter` or
309
- the `DetailedViolationFormatter`. Note that those are only intended for text-based interfaces such as
308
+ <1> To format the validation result into an human-readable form , use the `ViolationFormatter` or the
309
+ `DetailedViolationFormatter`. Note that those are only intended for text-based interfaces such as
310
310
CLIs.
311
311
<2> Every application dealing with validation results that needs to transform the results into some
312
312
different structure should instead implement the `Violation.Visitor` Interface with a suitable target
@@ -425,8 +425,7 @@ include::example$GenerateJsonPayload.java[tags=generate]
425
425
=== Generating JSON Schema
426
426
427
427
The JSON schema generator creates a https://json-schema.org/[JSON Schema] that describes the payload for an Aspect model
428
- as it could be returned by an Aspect that implements that Aspect model. Currently, the generated schema corresponds to
429
-
428
+ as it could be returned by an Aspect that implements that Aspect model.
430
429
431
430
++++
432
431
<details>
0 commit comments