Known-bugs-present-in-the-current-stable-version.md

@@ -3,9 +3,9 @@
 * The `keep_kalman_algo_if_singularity_is_detected` option of the `estimation` command does not work as advertised (option will be removed in Dynare 7)
 * The `discretionary_policy` command does not accept the `planner_discount_latex_name` option, contrary to what the documentation says (bug fixed in preprocessor@f7917e9bd4369f25a20ce81e617014fdfe4f5718)
 * The `outfile` option of the `smoother2histval` command would produce an incorrect file on models with two lags or more, leading to incorrect results when loading that file with `histval_file` (bug fixed in 618712ad9fb9a128545ae9ee8ca01ca2900a3af9)
-* The point forecasts triggered by `forecast` option of `estimation` did not take shock uncertainty into account (bug not yet fixed, see https://git.dynare.org/Dynare/dynare/-/merge_requests/2384)
+* The point forecasts triggered by `forecast` option of `estimation` did not take shock uncertainty into account (bug fixed in f03929f3)
 * Using the `forecast` command with a model solved at `order=2` with `varexo_det`, Dynare would return uncertainty bands based on a first-order approximation (bug not fixed, see #1940)
-* The results of mode-finding were not correctly stored in `oo_.posterior_mode` for shock and measurement error correlations (bug not yet fixed, see !2373)
+* The results of mode-finding were not correctly stored in `oo_.posterior_mode` for shock and measurement error correlations (bug fixed in 7a8d8539)
 
 ### Low priority bugs that won't be fixed soon:
 * Forecasts are only based on the DSGE-model, not the DSGE-VAR (bug not yet fixed; see #819)