emphasize that privatelink is optional (#309)

Author: corkrean

pages/authzed/concepts/private-networking.mdx

@@ -1,14 +1,18 @@
+import { Callout } from 'nextra/components'
+
 # Private Networking
 
 Private Networking is functionality exclusive to AuthZed Dedicated that restricts network access to internal networks.
 When enabled, connections that are not configured are rejected.
 
 By adding this additional layer of security, entire classes of security risk are eliminated because only trusted networks have access to the software powering your authorization systems.
 
-While completely optional, we recommend all users to secure their connections to SpiceDB using Private Networking.
-
 In the scenario you choose not to use Private Networking, AuthZed Dedicated can alternatively be configured for access over the open internet.
 
+<Callout type="info">
+  Private networking is recommended, but optional. Authzed Dedicated can be configured to allow for connecting from the public internet.
+</Callout>
+
 ## Architecture
 
 The following diagram models Private Networking on AWS using AWS PrivateLink:

pages/authzed/guides/setting-up-private-networking.mdx

@@ -1,11 +1,16 @@
 import { Steps } from 'nextra/components'
+import { Callout } from 'nextra/components'
 
 # Setting up Private Networking
 
 This guide walks through setting up AuthZed Dedicated [Private Networking].
 
 [Private Networking]: ../concepts/private-networking
 
+<Callout type="info">
+  Private networking is recommended, but optional. Authzed Dedicated can be configured to allow for connecting from the public internet.
+</Callout>
+
 ## AWS Steps
 
 <Steps>

vercel.json

@@ -78,4 +78,4 @@
       "permanent": false
     }
   ]
-}
+}