From 7ebbd348d82003e11543c38743e657876a2e3d6e Mon Sep 17 00:00:00 2001 From: Niranjan Abhyankar <35718043+NiranjanAbhyankar@users.noreply.github.com> Date: Tue, 26 Oct 2021 19:25:13 +0000 Subject: [PATCH] [FIX] developer/javascript_cheatsheet: fix a typo closes odoo/documentation#1518 X-original-commit: d9e2ab6febe4712eae0024942195f0c956eb0743 Signed-off-by: Antoine Vandevenne (anv) --- content/developer/reference/frontend/javascript_cheatsheet.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/developer/reference/frontend/javascript_cheatsheet.rst b/content/developer/reference/frontend/javascript_cheatsheet.rst index 9e377315b..82e7dda28 100644 --- a/content/developer/reference/frontend/javascript_cheatsheet.rst +++ b/content/developer/reference/frontend/javascript_cheatsheet.rst @@ -8,7 +8,7 @@ Javascript Cheatsheet There are many ways to solve a problem in JavaScript, and in Odoo. However, the Odoo framework was designed to be extensible (this is a pretty big constraint), and some common problems have a nice standard solution. The standard solution -has probably the advantage of being easy to understand for an odoo developers, +has probably the advantage of being easy to understand for an odoo developer, and will probably keep working when Odoo is modified. This document tries to explain the way one could solve some of these issues.