Closed nejraselimovic closed 3 years ago
@johanstokking sorry, this is not done yet. I just posted a question about V2 SaaS ->V3:
@johanstokking I'm confused here, isn't it that the V2 SaaS (which was a paid offering, correct me if I'm wrong) customers can migrate active sessions but only to paid offerings of V3 (and not the Community Edition)? If yes, why is that relevant for TTN community docs?
then I'll move forward with this.
I'm seeing here that we don't use Community Edition phrase, so I'll just rename it to The Things Network. I'm really trying to be consistent, but I didn't catch this one. Although I think that generally sticking to our official branding is a double-edged sword - that's why me and @laurensslats decided to keep for example "The Things Stack V3" instead of just "The Things Stack" in these guides.
@nejraselimovic let's also add a part at the beginning of the document, explaining the terms:
@laurensslats can you please do another round of review? I think I replaced all names in these pages, but this has to be done for all TTN documentation, so I'd like to check if this is the way to proceed.
The Things Stack, The Things Stack Community Edition and The Things Network V2 are mentioned in the beginning of the _index.md
file, let me know if that is enough.
Removing information about migrating active sessions and adding a note that it is available only for paid deployments. Ref: #442