Merge pull request #76 from orangci/main

refactor(docs-en): fix grammar issues and typos, add MX priority and TLSA documentation, and other errors

Author: iostpa

src/guides/cloudflare-pages.md

@@ -4,17 +4,17 @@ icon: /media/cloudflare.svg
 tags: guides
 ---
 
-# Setting up Cloudflare Pages with is-a-dev subdomain
+# Setting up Cloudflare Pages with an is-a.dev subdomain
 
-This guide will walk you through the process of setting up a Cloudflare Pages site and pointing your is-a.dev subdomain to it.
+This guide will walk you through the process of setting up a Cloudflare Pages website and pointing your is-a.dev subdomain towards it.
 
-## Create a Cloudflare Pages Site
+## Create a Cloudflare Pages Website
 
-First, you'll need to create a site on Cloudflare Pages. Follow the instructions in the [Cloudflare Pages Getting Started Guide](https://developers.cloudflare.com/pages/get-started/guide/).
+First, you'll need to create a website on Cloudflare Pages. Follow the instructions in the [Cloudflare Pages Getting Started Guide](https://developers.cloudflare.com/pages/get-started/guide/).
 
 ### Point your subdomain to your Cloudflare Pages site
 
-Next, you'll need to point your is-a.dev subdomain to your Cloudflare Pages site. Follow the instructions in the [Cloudflare Pages Custom Domains Guide](https://developers.cloudflare.com/pages/platform/custom-domains/#add-a-custom-domain). Only follow the "Add a custom domain" section, then return to this guide for the next steps.
+Next, you'll need to point your is-a.dev subdomain to your Cloudflare Pages website. Follow the instructions in the [Cloudflare Pages Custom Domains Guide](https://developers.cloudflare.com/pages/platform/custom-domains/#add-a-custom-domain). Only follow the "Add a custom domain" section, and then return to this guide for the next steps.
 
 ### Create the Domain File
 
@@ -24,14 +24,14 @@ In the `domains` directory, create a new JSON file for your subdomain (`domains/
 {
     "owner": {
         "username": "your-github-username",
-        "email": "your-email@gmail.com"
+        "email": "your-email@example.com"
     },
     "record": {
         "CNAME": "your-sitename.pages.dev"
     }
 }
 ```
 
-### Your site should be live!
+### Your website should be live!
 
-If you have followed all the steps correctly, then your site should be live after your pull request has been merged.
+If you have followed all the steps correctly, then your website should be live after your pull request has been merged.

src/guides/codeberg-pages.md

@@ -4,33 +4,33 @@ icon: /media/codeberg.svg
 tags: guides
 ---
 
-# Setting up Codeberg Pages with is-a-dev subdomain
+# Setting up Codeberg Pages with an is-a.dev subdomain
 
-This guide will walk you through the process of setting up a Codeberg Pages site and pointing your is-a.dev subdomain to it.
+This guide will walk you through the process of setting up a Codeberg Pages website and pointing your is-a.dev subdomain to it.
 
-## Create a Codeberg Pages Site
+## Create a Codeberg Pages Website
 
-First, you'll need to create a site on Codeberg Pages. Follow the instructions in the [Codeberg Pages Guide](https://docs.codeberg.org/codeberg-pages/).
+First, you'll need to create a website on Codeberg Pages. Follow the instructions in the [Codeberg Pages Guide](https://docs.codeberg.org/codeberg-pages/).
 
 ### Create the Domain File
 
-Create a JSON file inside domains directory (domains/subdomain.json) with the following content and submit a pull request:
+Create a JSON file inside domains directory (`domains/subdomain.json`) with the following content and submit a pull request:
 
 ```json
 {
     "owner": {
         "username": "your-codeberg-username",
-        "email": "your-email@gmail.com"
+        "email": "your-email@example.com"
     },
     "record": {
-        "CNAME": "pages.your-username.codeberg.page"
+        "CNAME": "pages.your-codeberg-username.codeberg.page"
     }
 }
 ```
 
 ### Add `.domains` file
 
-Once your PR is merged, Make a `.domains` file to point your website to your new .is-a.dev domain and add your subdomain (`your-subdomain.is-a.dev`) to it.
+Once your PR is merged, Make a `.domains` file to point your website to your new `.is-a.dev` domain and add your subdomain (`your-subdomain.is-a.dev`) to it.
 
 ### Done!
 

src/guides/dbh.md

@@ -4,13 +4,13 @@ tags: guides
 icon: /media/dbh.png
 ---
 
-# Setting up DanBot Hosting with is-a.dev subdomain
+# Setting up DanBot Hosting with an is-a.dev subdomain
 
-This guide will walk you through the process of setting up a DanBot Hosting site and pointing your is-a.dev subdomain to it.
+This guide will walk you through the process of setting up a DanBot Hosting website and pointing your is-a.dev subdomain to it.
 
 ## Getting Proxy IP
 
-Execute the following command in [DanBot Hosting Discord server](https://discord.gg/dbh) in the #commands channel.
+Execute the following command in [DanBot Hosting Discord server](https://discord.gg/dbh) in the `#commands` channel.
 
 ```
 dbh!server proxy
@@ -20,7 +20,7 @@ You will get a reply like this:
 
 ![](../media/dbh_proxy/1.jpg)
 
-If you are on free plan, choose any US proxy or you can use the Donator Proxy If you are a Donator, then note the IP address of the proxy you chose.
+If you are on a free plan, choose any US proxy or you can use the Donator Proxy If you are a Donator, note the IP address of the proxy you chose.
 
 ### Creating the domain file
 
@@ -40,11 +40,11 @@ Create a JSON file inside `domains` directory (`domains/subdomain.json`) with th
 }
 ```
 
-**Note:** In the owner section, you can add any social media handle, such as Discord. If you add another social media account, you can omit the email field. However, the GitHub username is mandatory. Don't forget to provide a preview of your site in your pull request.
+**Note:** In the owner section, you can add any social media handle, such as Discord. If you add another social media account, you may omit the email field. However, the GitHub username is mandatory. Don't forget to provide a preview of your website in your pull request.
 
 ## Configuring
 
-After the pull request is merged, get your server ID by running this command:
+After your pull request is merged, get your server ID by running this command:
 
 ```
 dbh!server list

src/guides/discord-verification.md

@@ -4,7 +4,7 @@ label: Discord Domain Connection
 tags: guides
 ---
 
-# Setting up Discord domain connection with your is-a.dev domain
+# Setting up Discord domain connection with your is-a.dev subdomain
 
 ## Get your verification string
 
@@ -33,8 +33,8 @@ Create a JSON file inside the `domains/` directory called `domains/_discord.exam
 ```json
 {
     "owner": {
-        "username": "github-username",
-        "email": "email@address"
+        "username": "your-github-username",
+        "email": "your-email-address@example.com"
     },
     "record": {
         "TXT": "discord-verification-string"
@@ -45,4 +45,4 @@ Create a JSON file inside the `domains/` directory called `domains/_discord.exam
 ## Configuration
 
 After your pull request has been merged, repeat the steps to get the verification string and press the `Verify` button.
-If it shows any error such as `Unable to verify your domain`, try waiting a few minutes (sometimes up to 24 hours) as the DNS might have not been updated yet.
+If it shows any error such as `Unable to verify your domain`, try waiting a few minutes (sometimes up to 24 hours) as the DNS might not have propagated yet.

src/guides/github-pages.md

@@ -4,7 +4,7 @@ icon: mark-github
 tags: guides
 ---
 
-## Setting up GitHub pages with is-a.dev subdomain
+## Setting up GitHub pages with an is-a.dev subdomain
 
 This guide will walk you through the process of setting up a GitHub Pages site and pointing your is-a.dev subdomain to it.
 
@@ -32,15 +32,15 @@ Create a JSON file inside `domains` directory (`domains/subdomain.json`) with th
 
 ### Configuring
 
-- After the pull request is merged, you may see a **404** error on `subdomain.is-a.dev` or the wrong site. To fix this, go to your GitHub pages repository's **Settings > GitHub pages > Custom Domain** and add `subdomain.is-a.dev` in the given field. _Only do this **after** your pull request is merged._
+- After the pull request is merged, you may see a **404** error on `subdomain.is-a.dev` or the wrong site. To fix this issue, go to your GitHub pages repository and navigate to: **Settings > GitHub pages > Custom Domain** and add `subdomain.is-a.dev` in the given field. *Only do this **after** your pull request is merged.*
 - Check the **Enforce HTTPS** checkbox below the custom domain input.
 - Wait some time and your site should be live!
 
-## Verifying your is-a.dev Domain with GitHub Pages
+## Verifying your is-a.dev Subdomain with GitHub Pages
 
 ### Get your verification string
 
-1. Open GitHub, press on your profile icon on the top right, and press `Settings`.
+1. Navigate to GitHub, press your profile icon at the top right, and press `Settings`.
 
 ![](../media/github_pages_verification/step_1.png)
 
@@ -52,7 +52,7 @@ Create a JSON file inside `domains` directory (`domains/subdomain.json`) with th
 
 ![](../media/github_pages_verification/step_3.png)
 
-4. In the field that appears, type your is-a.dev domain name (e.g. `myname.is-a.dev`) and press `Add domain`.
+4. In the field that appears, type your is-a.dev subdomain name (e.g. `myname.is-a.dev`) and press `Add domain`.
 
 ![](../media/github_pages_verification/step_4.png)
 
@@ -79,4 +79,4 @@ Create a JSON file inside the `domains/` directory called `domains/hostname.subd
 ### Configuration
 
 After your pull request has been merged, repeat the steps to get the verification string and press the `Verify` button.
-If it shows any error such as `Unable to verify your domain`, try waiting a few minutes (sometimes up to 24 hours) as the DNS change might not have reflected on the DNS server.
+If it shows an error such as `Unable to verify your domain`, try waiting a few minutes (sometimes up to 24 hours) as the DNS records may not have propagated yet.

src/guides/hashnode.md

@@ -6,7 +6,7 @@ tags: guides
 
 # Hashnode Blog
 
-When you create your Hashnode blog, Hashnode provides a free `hashnode.dev` subdomain for you. However, you can set up your own `is-a.dev` subdomain.
+When you create your Hashnode blog, Hashnode provides a free `hashnode.dev` subdomain for you. However, you can alternatively set up your own `is-a.dev` subdomain.
 
 In this guide, you will learn how to accomplish this.
 

src/guides/improvmx.md

@@ -4,20 +4,20 @@ icon: /media/improvmx.svg
 tags: guides
 ---
 
-# Setting up ImprovMX with is-a.dev subdomain
+# Setting up ImprovMX with an is-a.dev subdomain
 
 This guide will walk you through the process of setting up ImprovMX with your is-a.dev subdomain.
 
-## What you need to do before you continue.
+## Requirements
 
-1. Have a ImprovMX account. If you don't have a ImprovMX account, please go to [their site](https://improvmx.com) and make a account.
+1. You must have an ImprovMX account. If you don't have an ImprovMX account, please visit [their website](https://improvmx.com) and create an account.
 2. You should have already forked the [is-a.dev repository](https://github.com/is-a-dev/register). If you haven't forked the repository, please make one by using [this link](https://github.com/is-a-dev/register/fork).
 
-## Making the file.
+## Creating the file
 
-First go to the fork you've made, then go into the `domains` directory and make a file. The file should be named like this: `subdomain.json`. (Replace `subdomain` with the subdomain name you want of course.)
+Visit your fork and navigate into the `domains` directory and create a file. The file should be named in this manner: `subdomain.json`. (Replace `subdomain` with the subdomain name that you want.)
 
-After you've made the file, you should put in the file this:
+After you've made the file, it should look like this:
 ```json
 {
     "owner": {
@@ -31,8 +31,8 @@ After you've made the file, you should put in the file this:
 }
 ```
 
-**After you have made the file, you should make a pull request to the [is-a.dev repository](https://github.com/is-a-dev/register).**
+**After you've made the file, make a pull request to the [is-a.dev repository](https://github.com/is-a-dev/register).**
 
 ## Configuring
 
-After it has been merged, it should be automatically recognized and should start working. If you haven't configured it beforehand, please go to the [ImprovMX dashboard](https://app.improvmx.com/) and add the domain there.
+After your pull request has been merged, the MX records should be recognized automatically and start working. If you haven't configured it beforehand, please go to the [ImprovMX dashboard](https://app.improvmx.com/) and add the subdomain there.

src/guides/netlify.md

@@ -4,13 +4,13 @@ label: Netlify
 tags: guides
 ---
 
-# Setting up Netlify with is-a.dev Subdomain
+# Setting up Netlify with an is-a.dev Subdomain
 
-This guide will walk you through the process of setting up a Netlify deployment and pointing your is-a.dev subdomain to it.
+This guide will walk you through the process of setting up a Netlify deployment and pointing your is-a.dev subdomain towards it.
 
-## Creating a Netlify Site
+## Creating a Netlify Website
 
-First, you'll need to create a site on Netlify. Follow the instructions in the [Netlify Docs](https://docs.netlify.com/).
+First, create a website on Netlify. Follow the instructions in the [Netlify Docs](https://docs.netlify.com/).
 
 ### Creating the Domain File
 
@@ -30,15 +30,13 @@ Create a JSON file inside the `domains` directory (`domains/subdomain.json`) wit
 }
 ```
 
-**Note:** In the owner section, you can add any social media handle, such as Discord. If you add another social media account, you can omit the email field. However, the GitHub username is mandatory. Don't forget to provide a preview of your site in your pull request.
+**Note:** In the owner section, you can add any social media handle, such as Discord. If you add another social media account, you can omit the email field. However, the GitHub username is mandatory. Don't forget to provide a preview of your website in your pull request.
 
 ## Configuring Netlify
-
-- After the pull request is merged, you may need to configure your Netlify site to use the new subdomain. Go to your Netlify site's dashboard.
+- After your pull request is merged, you may need to configure your Netlify website to use the new subdomain. Visit your Netlify website's dashboard.
 - Navigate to **Site Settings > Domain Management > Custom Domains** and add `subdomain.is-a.dev` in the given field.
-- Netlify will provide a verification step, usually requiring you to add a DNS record. This step should be skipped if your subdomain is already pointing to Netlify's IP address (`75.2.60.5`).
+- Netlify will provide a verification step, usually requiring you to add a DNS record. You should be able to skip this step if your subdomain is already pointing to Netlify's IP address (`75.2.60.5`).
 
 ### Final Steps
-
 - Wait for the DNS changes to propagate. This can take from a few minutes to a couple of hours.
-- Your Netlify site should now be accessible at `subdomain.is-a.dev`.
+- Your Netlify website should now be accessible at `your-subdomain.is-a.dev`.

src/guides/other.md

@@ -8,10 +8,10 @@ tags: guides
 
 ## Setting up records
 
-Read the [domain file structure](../useful/domain-structure) and setup the records accordingly.
+Read the [domain file structure](../useful/domain-structure) and set up the records accordingly.
 
 ## Configuring your server
 
-After the pull request is merged, configure your server (apache, nginx, etc.) to work with `subdomain.is-a.dev`. If you are unsure how to configure your server, you can create an issue for support.
+After the pull request is merged, configure your server (apache, nginx, etc.) to work with `subdomain.is-a.dev`. If you are unsure how to configure your server, you can [create an issue](https://github.com/is-a-dev/register/issues/new/choose) for support.
 
-You should also, include `subdomain.is-a.dev` in your ssl certificate to get rid of certificate errors.
+You should also include `subdomain.is-a.dev` in your ssl certificate to get rid of certificate errors.

src/guides/railway.md

@@ -19,8 +19,8 @@ tags: guides
 ```json
 {
   "owner": {
-    "username": "your-username",
-    "email": "your-email"
+    "username": "your-github-username",
+    "email": "your-email@example.com"
   },
   "record": {
     "CNAME": "the-value-railway-gave-you"
@@ -29,9 +29,9 @@ tags: guides
 ```
 9. After you have made the file, you should make a pull request.
 !!!
-**Adding the website preview is neccessary**, since the CNAME value Railway gives you doesn't actually show you the website you are running.
+**Adding the website preview is mandatory**, since the CNAME value Railway gives you doesn't actually show you the website you are running.
 !!!
 
 
-**If the PR has been merged, the DNS records will be updated in a few minutes.**
-**If the PR has been merged but the DNS records haven't updated and you have waited 48 hours, open a GitHub issue or a help thread in the is-a.dev discord server.**
+- **If the PR has been merged, the DNS records will be updated in a few minutes.**
+- **If the PR has been merged but the DNS records haven't updated and you have waited 48 hours, [open a GitHub issue](https://github.com/is-a-dev/register/issues/new/choose) or a help thread in the is-a.dev [Discord server]((https://discord.gg/is-a-dev-830872854677422150)).**