From 86b53d90b05a60db7fda56d1ef02f04eb3c4efa1 Mon Sep 17 00:00:00 2001
From: Mike Auty <mike.auty@gmail.com>
Date: Mon, 9 Mar 2026 20:47:24 +0000
Subject: [PATCH] Update documentation to remove black and use ruff

---
 CODING_STYLE.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CODING_STYLE.md b/CODING_STYLE.md
index a4e248ffe..ed69003c6 100644
--- a/CODING_STYLE.md
+++ b/CODING_STYLE.md
@@ -5,7 +5,7 @@ The coding standards for volatility are mostly by our linter and our code format
 All code submissions will be vetted automatically through tests from both and the submission will not be accepted if either of these fail.
 
 Code Linter: Ruff
-Code Formatter: Black
+Code Formatter: Ruff
 
 In addition, there are some coding practices that we employ to prevent specific failure cases and ensure consistency across the codebase.  These are documented below along with the rationale for the decision.