From d44f43c20518d519ab20f959a4398afa54166015 Mon Sep 17 00:00:00 2001 From: Raimund Klein <770876+Chessray@users.noreply.github.com> Date: Thu, 4 Jan 2024 14:13:28 +0000 Subject: [PATCH] Update content/faq/_index.md Co-authored-by: Filip Hrisafov --- content/faq/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/faq/_index.md b/content/faq/_index.md index 8b85f07f5..f27829f87 100644 --- a/content/faq/_index.md +++ b/content/faq/_index.md @@ -348,7 +348,7 @@ concepts, your options are: * Instead of supplying a `@Context` object as parameter, consider injecting it. * If injecting the object is no option, sometimes you may be able to inject some form of modifiable wrapper object that - can be given the `@Contet` object at runtime. + can be given the `@Context` object at runtime. * If neither of the above two are possible and you can't implement a mapping without a `@Context` object, you should stick to MapStruct's core functionality and refrain from letting this particular Mapper extend the `Converter` interface.