From f3b5514579738c4441164acdec95d83a580a098f Mon Sep 17 00:00:00 2001 From: Nico Schottelius Date: Thu, 20 Jan 2022 14:12:53 +0100 Subject: [PATCH] Title changes --- .../u/blog/2022-01-20-to-viirb-or-not-to-viirb/contents.lr | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/u/blog/2022-01-20-to-viirb-or-not-to-viirb/contents.lr b/content/u/blog/2022-01-20-to-viirb-or-not-to-viirb/contents.lr index 4c3ff25..c6b68cf 100644 --- a/content/u/blog/2022-01-20-to-viirb-or-not-to-viirb/contents.lr +++ b/content/u/blog/2022-01-20-to-viirb-or-not-to-viirb/contents.lr @@ -92,7 +92,9 @@ And the answer is "Jein" (a German combination of "Ja" + "Nein"): * Financially it doesn't * For supporting IPv6 deployments world wide: it does -To continue providing VIIRB and VIWIB, we have two +To continue providing VIIRB and VIWIB, we have decided on two +strategies: + ### Introducing the "Fair Price" @@ -107,7 +109,7 @@ call them now "Sponsored Price". Obviously we encourage everyone who can to buy the devices at the fair price, but if you can't, we will continue to sponsor IPv6 deployments. -### VIIRB+VIWIB Sponsoring package +### Adding VIIRB+VIWIB Sponsoring package Secondly we know offer VIIRB and VIWIB sponsoring packages: If you think what we do is a good thing and you would like to support it, we