From 9a58ede42fcf35397c7bd6b82f58a358c3bef6ec Mon Sep 17 00:00:00 2001
From: plebhash <147345153+plebhash@users.noreply.github.com>
Date: Mon, 2 Dec 2024 10:02:01 -0300
Subject: [PATCH] Update 05-Mining-Protocol.md

Co-authored-by: bit-aloo <84662239+Shourya742@users.noreply.github.com>
---
 05-Mining-Protocol.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/05-Mining-Protocol.md b/05-Mining-Protocol.md
index 5570d74..68e7704 100644
--- a/05-Mining-Protocol.md
+++ b/05-Mining-Protocol.md
@@ -29,7 +29,7 @@ Mining servers MUST assign a unique subset of the search space to each mining de
 
 This protocol explicitly expects that upstream server software is able to manage the size of the hashing space correctly for its clients and can provide new and unique Jobs quickly enough, based on the hashpower of each client.
 
-The protocol defines two main types of Jobs: **Standard Jobs** and **Extended Jobs**.
+The protocol defines two main types of Jobs: **Standard Job** and **Extended Job**.
 
 This separation vastly simplifies the protocol implementation for clients that don’t support Extended Job, as they only need to implement the subset of protocol messages related to Standard Job (see Mining Protocol Messages for details).