From fada1860058ec05d4159196c1828355acb24d284 Mon Sep 17 00:00:00 2001
From: jkrvivian <jkrvivian@gmail.com>
Date: Thu, 23 Nov 2023 21:29:44 +0800
Subject: [PATCH] Rename Version Signaling to Version Signaling Parameters

---
 tips/TIP-0049/tip-0049.md | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/tips/TIP-0049/tip-0049.md b/tips/TIP-0049/tip-0049.md
index b595ca5d2..0ef1d16d0 100644
--- a/tips/TIP-0049/tip-0049.md
+++ b/tips/TIP-0049/tip-0049.md
@@ -364,11 +364,11 @@ other nodes and to process blocks properly.
     </td>
   </tr>
   <tr>
-    <td valign="top">Version Signaling <code>oneOf</code></td>
+    <td valign="top">Version Signaling Parameters <code>oneOf</code></td>
     <td colspan="2">
       <details open="true">
-        <summary>Version Signaling</summary>
-        <blockquote>Version Signaling defines the parameters used by signaling protocol parameters upgrade.</blockquote>
+        <summary>Version Signaling Parameters</summary>
+        <blockquote>Version Signaling Parameters defines the parameters used by signaling protocol parameters upgrade.</blockquote>
         <table>
           <tr>
             <td>
@@ -458,7 +458,6 @@ other nodes and to process blocks properly.
     <td>Target Committee Size defines the target size of the committee. If there's fewer candidates the actual committee size could be smaller in a given epoch.</td>
   </tr>
 </table>
-
 When referring to Protocol Parameters contained in subschemas in other TIPs, one may use namespacing with a `::`
 separator for disambiguation. For instance, `Work Score Parameters::Block` refers to the `Block` parameter inside the
 `Work Score Parameters`.
@@ -537,7 +536,7 @@ The example is a protocol parameter filled with random values:
     "maxBufferSize": 1000,
     "maxValidationBufferSize": 100
   },
-  "versionSignaling": {
+  "versionSignalingParameters": {
     "windowSize": 7,
     "windowTargetRatio": 5,
     "activationOffset": 7