From 796b440f931003571a9cf6c3a9e47785bfad858f Mon Sep 17 00:00:00 2001 From: Graham McIntire Date: Sat, 18 Apr 2026 16:08:46 -0500 Subject: [PATCH] Fix typo and reflow paragraph in prop1 post --- content/blog/prop1.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/blog/prop1.md b/content/blog/prop1.md index 11a8ab7..454a818 100644 --- a/content/blog/prop1.md +++ b/content/blog/prop1.md @@ -9,7 +9,7 @@ From running a WISP I'm very familiar with point-to-point microwave links. Howev amateur radio operators have been making NLOS contacts for years when they technically shouldn't work at all. -As an example, this is the evelation path between my QTH and an [NTMS beacon on top of Texas +As an example, this is the elevation path between my QTH and an [NTMS beacon on top of Texas Women's University's dorm building](https://prop.w5isp.com/beacons/dddca785-c3e7-45f8-8f9f-edc748f881d6): ![Path profile](/images/path_profile.png) @@ -29,7 +29,8 @@ claude to write out some client-side pages to help predict and analyze the propa on limited data, but did an okay job guessing at why the propagation worked. Fast forward a few weeks and I've now build an elixir/phoenix app at that -collects and processes everything. For a quick import of some known contacts made, I imported all of the ARRL 10 GHz and up contests as well as the 222 MHz and up contests. +collects and processes everything. For a quick import of some known contacts made, I imported all +of the ARRL 10 GHz and up contests as well as the 222 MHz and up contests. With known contacts in place, it was time to backfill them with data, including: