commit d5229bfc2be2596b4f761e924867bf56472006c9
parent d2ee8d0cb6725819e5902c11077d7a4eea51621e
Author: iostpa <iostpa@iostpa.com>
Date: Tue, 28 Oct 2025 19:55:12 +0200
orangc nitpick
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/useful/quickstart.md b/src/useful/quickstart.md
@@ -22,7 +22,7 @@ After you've forked our repository, you can start making the file for your domai
You may be wondering, "How should I name the file?" The filename should be the domain name you want in lowercase followed by the JSON extension (.json) at the end of the filename, so it would be something like this: `subdomain.json` (Replace `subdomain` with the name you want to register, of course). For more information about what filenames are valid or invalid, click [here](https://docs.is-a.dev/domain-structure/#-filename-guidelines).
-After you've finished with the filename, you can start making the file format of the JSON file. Now depending on your hosting provider, we have guides for most hosting providers (like GitHub Pages, Cloudflare Pages and Vercel, just to name a few) accessible in our documentation, but for hosting providers that don't have a guide, you should pay attention to what records they provide. An example of a valid file format is the one listed below, though you can also check out the [Domain Structure](useful/domain-structure) section to see what records we support.
+After you've finished with the filename, you can start making the file format of the JSON file. Depending on your hosting provider, we have guides for most hosting providers (like GitHub Pages, Cloudflare Pages and Vercel, just to name a few) accessible in our documentation, but for hosting providers that don't have a guide, you should pay attention to what records they provide. An example of a valid file format is the one listed below, though you can also check out the [Domain Structure](useful/domain-structure) section to see what records we support.
```json
{
