From 84062bf78fe17af331f31b4f35a9133ff82d7f36 Mon Sep 17 00:00:00 2001 From: fml2 Date: Mon, 9 Dec 2019 13:49:57 +0100 Subject: [PATCH] docs: Fix typo in the builder section --- .../src/main/asciidoc/chapter-3-defining-a-mapper.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/src/main/asciidoc/chapter-3-defining-a-mapper.asciidoc b/documentation/src/main/asciidoc/chapter-3-defining-a-mapper.asciidoc index 335bbbf95..5255ac6f1 100644 --- a/documentation/src/main/asciidoc/chapter-3-defining-a-mapper.asciidoc +++ b/documentation/src/main/asciidoc/chapter-3-defining-a-mapper.asciidoc @@ -422,7 +422,7 @@ The default implementation of the `BuilderProvider` assumes the following: * The type has a parameterless public static builder creation method that returns a builder. So for example `Person` has a public static method that returns `PersonBuilder`. -* The builder type has a parameterless public method (build method) that returns the type being build +* The builder type has a parameterless public method (build method) that returns the type being built. In our example `PersonBuilder` has a method returning `Person`. * In case there are multiple build methods, MapStruct will look for a method called `build`, if such method exists then this would be used, otherwise a compilation error would be created. @@ -527,4 +527,4 @@ Otherwise, you would need to write a custom `BuilderProvider` [TIP] ==== In case you want to disable using builders then you can use the `NoOpBuilderProvider` by creating a `org.mapstruct.ap.spi.BuilderProvider` file in the `META-INF/services` directory with `org.mapstruct.ap.spi.NoOpBuilderProvider` as it's content. -==== \ No newline at end of file +====