Removes unnecessary pre-req and wrong TCP statement

Author: mikenomitch

src/content/docs/containers/architecture.mdx

@@ -62,6 +62,5 @@ which will allow container instances to always run in the same location as their
 :::
 
 Because all Container requests are passed through a Worker, end-users cannot make TCP or
-UDP requests to a Container instance. Workers themselves can make TCO and UDP requests to
-the Container using the [`connect()` API](/workers/runtime-apis/tcp-sockets/#connect). If you have a use
-case that requires inbound TCP or UDP from an end-user, please [let us know](https://forms.gle/AGSq54VvUje6kmKu8).
+UDP requests to a Container instance. If you have a use case that requires inbound TCP
+or UDP from an end-user, please [let us know](https://forms.gle/AGSq54VvUje6kmKu8).

src/content/docs/containers/get-started.mdx

@@ -14,21 +14,6 @@ This example Worker should give you a sense for simple Container use, and provid
 
 ## Prerequisites
 
-### Get an API Token with the correct permissions
-
-Ensure your account (or manually provided token) has the correct permissions to deploy a Worker with Containers.
-
-If you have admin-level permissions, this should happen automatically.
-
-If you have a custom token or a user with specific privledges, you must have the following permissions:
-
-- "Containers: Edit"
-- "Workers Scripts: Edit"
-
-Refer to [Find zone and account IDs](/fundamentals/account/find-account-and-zone-ids) for help locating
-your Account ID and [Create an API token](/fundamentals/api/get-started/create-token) to learn how to create
-an access your API token.
-
 ### Ensure Docker is running locally
 
 In this guide, we will build and push a container image alongside your Worker code. By default, this process uses