From 1877fea733568c7279f274f22e4575f4dc57b016 Mon Sep 17 00:00:00 2001
From: SevicheCC <91365763+Sevichecc@users.noreply.github.com>
Date: Thu, 8 Jun 2023 16:00:19 +0800
Subject: [PATCH] Update README.md

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

diff --git a/README.md b/README.md
index 9dcfb30..0e701c6 100644
--- a/README.md
+++ b/README.md
@@ -25,7 +25,7 @@ Misskey's implementation is more complex and is currently pending due to this is
 
 Access tokens are frequently used in development, but Akkoma and Pleroma lack an intuitive way to obtain one, unlike Mastodon. The only way to create an application and get an account's access token is to mock HTTP requests using tools like Postman. Since the HTTP request body is highly flexible, it can contain typos or other errors, and changing authorization scopes is not convenient. Pleroma's available authorization scopes are not as clear as Mastodon's, which sometimes leads to setting overly broad permissions, compromising user security and violating the principle of minimal authorization scope.
 
-To address this issue, I wanted Akkoma to have an easy way to register a client app and obtain an access token for testing. I opened an issue on [Akkoma-fe](https://akkoma.dev/AkkomaGang/akkoma-fe/issues/296), but it has been pending for about a month without any response from the developer. As a result, I created this project.
+To address this issue, I wanted Akkoma to have an easy way to register a client app and obtain an access token for testing. I opened an [issue](https://akkoma.dev/AkkomaGang/akkoma-fe/issues/296) on Akkoma-fe, but it has been pending for about a month without any response from the developer. As a result, I created this project.
 
 This app is inspired by the [Access Token Generator for Pleroma](https://tools.splat.soy/pleroma-access-token/) API, but offers more features, such as finer-grained admin scopes, no analytics, and no data storage in local storage, making it a safer option.