From 7536f3aaa41f3eccc16c399823a94c8360de0676 Mon Sep 17 00:00:00 2001
From: Tim Beiko <9390255+timbeiko@users.noreply.github.com>
Date: Fri, 27 Dec 2024 09:27:49 -0800
Subject: [PATCH] Update EIP-7723: Escape Latex

Merged by EIP-Bot.
---
 EIPS/eip-7723.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/EIPS/eip-7723.md b/EIPS/eip-7723.md
index 5c0bb845539b24..56e575c4515fc6 100644
--- a/EIPS/eip-7723.md
+++ b/EIPS/eip-7723.md
@@ -33,7 +33,7 @@ Before the Upgrade Meta EIP is moved to `Final`, the `Scheduled for Inclusion` s
 
 ### Upgrade Devnets
 
-When preparing a network upgrade, client developers typically implement EIPs first on an ephemeral test network (upgrade devnet) to verify client interoperability, before deploying to long-lived test networks. These upgrade devnets follow a naming convention of $upgradeName-devnet-$version (e.g. pectra-devnet-0 for the first upgrade devnet of the Pectra network upgrade, dencun-devnet-1 for the second upgrade devnet of the Dencun update, etc).
+When preparing a network upgrade, client developers typically implement EIPs first on an ephemeral test network (upgrade devnet) to verify client interoperability, before deploying to long-lived test networks. These upgrade devnets follow a naming convention of \$upgradeName-devnet-\$version (e.g. pectra-devnet-0 for the first upgrade devnet of the Pectra network upgrade, dencun-devnet-1 for the second upgrade devnet of the Dencun update, etc).
 
 Since client developers' ability to include EIPs in a network upgrade is constrained by what can be implemented and tested in these upgrade devnets, the [Considered for Inclusion](#considered-for-inclusion) and [Scheduled for Inclusion](#scheduled-for-inclusion) sections below propose aligning these statuses with EIPs' implementation status in upgrade devnets.