From baaabd25c6d373f2a9f24ab8fd3c70cde33db027 Mon Sep 17 00:00:00 2001
From: Dmitry <98899785+mdqst@users.noreply.github.com>
Date: Mon, 23 Dec 2024 16:35:16 +0300
Subject: [PATCH] doc: fix finalizeWithoutProof() call Update release-notes.mdx

---
 docs/release-notes.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/release-notes.mdx b/docs/release-notes.mdx
index 9516c8054..e92ef788f 100644
--- a/docs/release-notes.mdx
+++ b/docs/release-notes.mdx
@@ -465,7 +465,7 @@ To support these new features, we implemented changes to our smart contracts.
 We introduce a `VERIFIER_SETTER_ROLE`, that will be attributed to the Timelock.sol so that all core
 contract upgrades (Rollup and Message and Token bridge) and verifiers are executed through a TimeLock mechanism.
 Note that we are also using this upgrade to update the way the type 2 state was calculated; as such we'll
-need to call `finalizeWithoutProof` to perform a state transition from type2 state v1 to type2 state v2.
+need to call `finalizeWithoutProof()` to perform a state transition from type2 state v1 to type2 state v2.
 
 The Security Council will first execute the following transactions on L1:
 - Assign Operator Role via the Safe to the account for blob submission
@@ -481,7 +481,7 @@ The Security Council will then execute the following transactions on L2:
 - Execute L2MessageService upgrade
 
 Post upgrade, Execute the following Security Council transactions on L1:
-- Call FinalizeWithoutProof
+- Call `finalizeWithoutProof()`
 - Clear verifier mapping at index 6 and 7
 
 The audited commit for this update can be found