From 00c1ae3e30c0f6c9383aa9ae5f9050839bd294c4 Mon Sep 17 00:00:00 2001 From: Christoph Date: Tue, 12 Nov 2024 21:15:12 +0100 Subject: [PATCH] Update docs/decisions/0039-use-apache-velocity-as-template-engine.md Co-authored-by: Subhramit Basu Bhowmick --- docs/decisions/0039-use-apache-velocity-as-template-engine.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/decisions/0039-use-apache-velocity-as-template-engine.md b/docs/decisions/0039-use-apache-velocity-as-template-engine.md index fd5d53ea7ef..46435540836 100644 --- a/docs/decisions/0039-use-apache-velocity-as-template-engine.md +++ b/docs/decisions/0039-use-apache-velocity-as-template-engine.md @@ -109,6 +109,6 @@ Here are the papers you are analyzing: As stated in [the template discussion issue](https://github.com/koppor/jabref/issues/392), we should choose a template engine, and then slowly migrate previous code and templates to the chosen engine. Other template engines are discussed at , especially [`#other-template-engines`](https://www.baeldung.com/spring-template-engines#other-template-engines). -We did not find any other engine there being worth switchting. +We did not find any other engine there worth switching to.