From f91d2aafa227dd24dc517a14aee215c554865ccc Mon Sep 17 00:00:00 2001 From: Sami Mokaddem Date: Fri, 19 Jun 2020 08:43:28 +0200 Subject: [PATCH] Fix typo --- _posts/2020-06-19-MISP.2.4.127.released.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2020-06-19-MISP.2.4.127.released.md b/_posts/2020-06-19-MISP.2.4.127.released.md index 17b7dac..d816e13 100644 --- a/_posts/2020-06-19-MISP.2.4.127.released.md +++ b/_posts/2020-06-19-MISP.2.4.127.released.md @@ -14,7 +14,7 @@ In MISP 2.4.116, a decaying functionality was added to allow users and organisat Based on the feedback of the organisations relying on the decaying feature, the following improvements were included: -- New setting `default_restsearch_parameters` allowing users to supply restSearch parameters that will be automatically be passed during API fetch. The main purpose of this new setting is to enable users to inject filters when integrating with third-party tools not offering the possibility to control the query performed against MISP. This for example allow to add default decaying parameters to all restSearch query done. +- New setting `default_restsearch_parameters` allowing users to supply restSearch parameters that will be automatically be passed during API fetch. The main purpose of this new setting is to enable users to inject filters when integrating with third-party tools not offering the possibility to control the query performed against MISP. For example, it allows to add default decaying parameters to all restSearch query done. - New setting `tag_numerical_value_override` allowing users to override the `numerical_value` if tags. The main purpose of this new setting is to let users have their own numerical values for tags. It does not constrain site-admin to diverge from the official misp-taxonomy repository, and let them define new values for entries not having one.