From a484e90253fee3a779155d54eb27a1b55afbf1b3 Mon Sep 17 00:00:00 2001
From: Shahriar <31452340+ShahriarKh@users.noreply.github.com>
Date: Tue, 16 Apr 2024 13:22:19 +0330
Subject: [PATCH] Update README.md

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

diff --git a/README.md b/README.md
index 2fe3c65..a41647d 100644
--- a/README.md
+++ b/README.md
@@ -311,7 +311,7 @@ Here are the cons:
 #### Versioning Schemes
 A pragmatic versioning scheme completes the overall API versioning strategy and addresses how to format the version number, when to upgrade and when to retire a version:
 
-* We will base our approach on Semantic Versioning ([semver](http://semver.org/)) and Fear-Driven Versioning ([ferver](https://github.com/jonathanong/ferver)).
+* We will base our approach on Semantic Versioning ([semver](http://semver.org/)) and Fear-Driven Versioning ([ferver](https://github.com/jaredly/ferver)).
 * We will only use a Major and Minor version in the form `x.y`, where `x` >= 1 and represents the Major version number, and `y` >= 0 and represents the Minor version number.
   * We never have a Major version of 0 because it makes the API appear unstable.
 * There is no need to modify either the Major or Minor version for Non-Breaking changes.