Simplify Connect firewall requirements

As there's no real distinction between authenticated and unauthenticated
requests to the Connect API (aside from a one or two extra HTTP headers)
from the perspective of a network administrator, combine those into a
single list item.

Author: mudge

documentation/asciidoc/services/connect/troubleshooting.adoc

@@ -82,8 +82,7 @@ If Connect can communicate properly on your network, you should see output simil
 
 If Connect can't communicate properly on your network, you'll see an "x" instead of a check next to the failing test case. Ask your network administrator to enable the following connections on your network:
 
-* unauthenticated HTTPS requests to the Raspberry Pi Connect API on port 443 of `api.connect.raspberrypi.com` 
-* authenticated requests to the Raspberry Pi Connect API on port 443 of `api.connect.raspberrypi.com`
+* HTTPS requests to the Raspberry Pi Connect API on port 443 of `api.connect.raspberrypi.com`
 * requests to Raspberry Pi Connect STUN or TURN servers on UDP port 3478 of all of the following:
 ** `stun.raspberrypi.com`
 ** `turn1.raspberrypi.com`