From 60115502259f48faeb92e6f7cbf94d216395a043 Mon Sep 17 00:00:00 2001
From: Erudition <3915447+Erudition@users.noreply.github.com>
Date: Wed, 16 Oct 2024 00:44:48 +0000
Subject: [PATCH] Address "BLS" vs "BLS12" confusion (#361)

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

diff --git a/README.md b/README.md
index 15d76ba3..e2a01e4c 100644
--- a/README.md
+++ b/README.md
@@ -62,7 +62,7 @@ This ["first come, first assign"](https://github.com/multiformats/multicodec/pul
 
 The first 127 bits are encoded as a single-byte varint, hence they are reserved for the most widely used multicodecs. So if you are adding your own codec to the table, you most likely would want to ask for a codec bigger than `0x80`.
 
-Codec names should be easily convertible to constants in common programming languages using basic transformation rules (e.g. upper-case, conversion of `-` to `_`, etc.). Therefore they should contain alphanumeric characters, with the first character being alphabetic. The primary delimiter for multi-part names should be `-`, with `_` reserved for cases where a secondary delimiter is required. For example: `bls12_381-g1-pub` contains 3 parts: `bls_381`, `g1` and `pub`, where `bls_381` is "BLS 381" which is not commonly written as "BLS381" and therefore requires a secondary separator.
+Codec names should be easily convertible to constants in common programming languages using basic transformation rules (e.g. upper-case, conversion of `-` to `_`, etc.). Therefore they should contain alphanumeric characters, with the first character being alphabetic. The primary delimiter for multi-part names should be `-`, with `_` reserved for cases where a secondary delimiter is required. For example: `bls12_381-g1-pub` contains 3 parts: `bls12_381`, `g1` and `pub`, where `bls12_381` is "BLS12 381" which is not commonly written as "BLS12381" and therefore requires a secondary separator.
 
 The `validate.py` script can be used to validate the table once it's edited.