From c27c4d38255863a520290b996b2f3a9652da2419 Mon Sep 17 00:00:00 2001 From: YoshiRulz Date: Sat, 28 Jun 2025 14:09:51 +1000 Subject: [PATCH] Update rotted internal links in documentation fixes 6212a7832 (PR #597) --- Documentation/README.md | 4 ++-- README.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/README.md b/Documentation/README.md index 21227223..090e09cc 100644 --- a/Documentation/README.md +++ b/Documentation/README.md @@ -12,8 +12,8 @@ The wiki is where you can find out information about using the software, the cod * [Open Location Code Overview](Specification/olc_definition.adoc) * [Open Location Code Specification](Specification/specification.md) -* [Guidance for Shortening Codes](Specification/Short_Code_Guidance.md) -* [Open Location Code Reference API](Specification/API.md) +* [Guidance for Shortening Codes](Specification/specification.md#generating-short-codes) +* [Open Location Code Reference API](Specification/specification.md#api-requirements) * [Plus Codes and Open Location Code Naming Guidelines](Specification/Naming_Guidelines.md) ### Technical diff --git a/README.md b/README.md index a9ff8fb4..c5dcd5af 100644 --- a/README.md +++ b/README.md @@ -74,7 +74,7 @@ Rather than a large city size feature to generate the reference location, it is better to use smaller, neighbourhood features, that will not have as much variation in their geocode results. -Guidelines for shortening codes are in the [wiki](Documentation/Specification/Short_Code_Guidance.md). +Guidelines for shortening codes are in the [wiki](Documentation/Specification/specification.md#generating-short-codes). Recovering shortened codes works by providing the short code and a reference location. This does not need to be the same as the location used to shorten the