From 08d297a15d55d6b7a9ff5fa0a4e14dea461b7200 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Aleks=20R=C5=ABti=C5=86=C5=A1?= Date: Fri, 14 Feb 2025 03:37:47 +0000 Subject: [PATCH] high-falutin' grammar --- posts/2025-02-13-go-module-imports.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/2025-02-13-go-module-imports.md b/posts/2025-02-13-go-module-imports.md index 52242eb..ff85973 100644 --- a/posts/2025-02-13-go-module-imports.md +++ b/posts/2025-02-13-go-module-imports.md @@ -5,7 +5,7 @@ published_on: '2025-02-13' Go modules are great. URL-based imports, generally, are great. One of the things that makes them so great is that putting them on your own domain provides a good way of verifying ownership without going through a third party or a complicated review process. Plus, it looks cool. -So, how exactly do you do such a thing? Well, it's [buried in the documentation](https://pkg.go.dev/cmd/go#hdr-Remote_import_paths), but it's really pretty simple. For each import path (e.g. `mysite.com/mypackage`), just put a page on your website with a `go-import` meta tag: +So, how exactly does one accomplish such a thing? Well, it's [buried in the documentation](https://pkg.go.dev/cmd/go#hdr-Remote_import_paths), but it's really pretty simple. For each import path (e.g. `mysite.com/mypackage`), just put a page on your website with a `go-import` meta tag: ```html