Update README.md

Author: harys722

README.md

@@ -1,6 +1,6 @@
 <div align="center">
   <a href="#">
-    <img src="https://harys722.github.io/github-guides/media/logo.png" alt="GitHub Logo" width="80" height="80">
+    <img src="https://harys722.github.io/github-guides/media/logo.png" alt="Logo" width="120" height="120">
   </a>
 
   <h1 align="center">GitHub Guides</h1>
@@ -54,7 +54,7 @@ This guide will walk you through the process of connecting your username.github.
 
 
 ### Configuration
-Now that you have the Discord verification TXT string, you need to fork this [repository](https://github.com/harys722/.well-known/). After forking this repository, go to this [file](https://github.com/harys722/.well-known/blob/main/discord) and remove everything and then paste your Discord verification string there. Once you paste it, commit the changes to save the file. After doing all these steps, repeat steps 1-5 and press the verify button. If it shows an error like `Unable to verify your domain`, try waiting a few minutes (sometimes up to 24 hours) as the records may not have propagated yet.
+Now that you have the Discord verification TXT string, you need to fork this [repository](https://github.com/harys722/.well-known/). After forking this repository, go to `discord` file and remove everything and then paste your Discord verification string there. Once you paste it, commit the changes to save the file. After doing all these steps, repeat steps 1-5 and press the verify button. If it shows an error like `Unable to verify your domain`, try waiting a few minutes (sometimes up to 24 hours) as the records may not have propagated yet. It usually takes less than 2 minutes.
 
 You can also create your own repository instead of forking this [repository](https://github.com/harys722/.well-known/). To create your own repository, read through GitHub's official guide [Creating a new repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-new-repository). The repository name **must** be `. well-known` and must contain the `discord` file with only your Discord verification TXT string content, otherwise the setup will not work properly.
 
@@ -91,7 +91,7 @@ This guide will walk you through the process of setting up your custom username.
 
 
 ### Configuration
-This setup will remain the same as the Discord domain connection guide, but we will mention it again here to prevent incomprehensible issues. Now that you have the Bluesky verification TXT string, you need to fork this [repository](https://github.com/harys722/.well-known/). After forking this repository, go to this [file](https://github.com/harys722/.well-known/blob/main/atproto-did) and remove everything and then paste your Bluesky verification string there. Once you paste it, commit the changes to save the file. After doing all these steps, repeat steps 1-5 and press the `Verify DNS Record` button. If it shows an error like `Failed to verify handle. Please try again.`, try waiting a few minutes (sometimes up to 24 hours) as the records may not have propagated yet.
+This setup will remain the same as the Discord domain connection guide, but we will mention it again here to prevent incomprehensible issues. Now that you have the Bluesky verification TXT string, you need to fork this [repository](https://github.com/harys722/.well-known/). After forking this repository, go to this `atproto-did` and remove everything and then paste your Bluesky verification string there. Once you paste it, commit the changes to save the file. After doing all these steps, repeat steps 1-5 and press the `Verify DNS Record` button. If it shows an error like `Failed to verify handle. Please try again.`, try waiting a few minutes (sometimes up to 24 hours) as the records may not have propagated yet.
 
 You can also create your own repository instead of forking this [repository](https://github.com/harys722/.well-known/). To create your own repository, read through GitHub's official guide [Creating a new repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-new-repository). The repository name **must** be `. well-known` and must contain the `atproto-did` file with only your Bluesky verification TXT string content, otherwise the setup will not work properly.