From 826328ec1491829e660d7fbec8972524f8ccccc2 Mon Sep 17 00:00:00 2001
From: Marcin Rataj <lidel@lidel.org>
Date: Thu, 26 Jul 2018 22:40:45 +0200
Subject: [PATCH] docs: removed IPNS in subdomain

Missed the fact IPNS does not work in case-insensitive contexts right now.
More: https://github.com/ipfs/go-ipfs/issues/5287
---
 ADDRESSING.md | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/ADDRESSING.md b/ADDRESSING.md
index 3e2b7c1..ecda00f 100644
--- a/ADDRESSING.md
+++ b/ADDRESSING.md
@@ -23,13 +23,11 @@
 When site isolation does not matter gateway can expose IPFS namespaces as regular URL paths:
 
     https://<gateway-host>.tld/ipfs/<cid>/path/to/resource
-    https://<gateway-host>.tld/ipns/<cid>/path/to/resource
+    https://<gateway-host>.tld/ipns/<keyid_or_fqdn>/path/to/resource
 
 When origin-based security perimeter is needed, [CIDv1](https://github.com/ipld/cid#cidv1) in Base32 ([RFC4648](https://tools.ietf.org/html/rfc4648#section-6), no padding) should be used in subdomain:
 
     https://<cidv1-base32>.ipfs.<gateway-host>.tld/path/to/resource
-    https://<peerid-base32>.ipns.<gateway-host>.tld/path/to/resource
-
 
 For more context see [notes on addressing with HTTP](#notes-on-addressing-with-http) below.