docs(serverless): clarify ports usage int-fix-serverless (#4577)

* fix(serverless): a port is not related to the HTTP protocol

* fix(serverless): add EOL

* fix(serverless): remove confusing sentence about different port

Indeed, we don't specificy what 'different' means here: from a default value?

* feat(serverless): explain that containers are accessible on ports 80 and 443 from the internet

* fix(serverless): apply sugession

Co-authored-by: Benedikt Rollik <[email protected]>

---------

Co-authored-by: Benedikt Rollik <[email protected]>

Author: ahamez

pages/serverless-containers/concepts.mdx

@@ -148,12 +148,13 @@ The container can then process the message and perform any required actions, suc
 
 ## Port
 
-The port parameter specifies the network port that your container listens on for incoming requests. If your application or container is set up to listen on a different port, you must specify it using the port parameter when deploying your container to Serverless Containers. It must reflect the port configuration within your container for your service to function correctly.
+The port parameter specifies the network port that your container listens on for incoming requests. It must reflect the port configuration within your container for your service to function correctly.
 
 The value defined in the port parameter will then be passed to your container during the deployment inside the `PORT` environment variable.
 
 <Message type="note">
-Only one HTTP port can be exposed per Serverless Container.
+- Only one port can be exposed per Serverless Container.
+- Your container is accessible from the internet via ports 80 and 443, regardless of the specified port. The value you set determines how the Scaleway infrastructure accesses your container.
 </Message>
 
 ## Privacy policy
@@ -262,4 +263,4 @@ Unit used to measure the resource consumption of a container. It reflects the am
 
 ## Protocol
 
-Serverless Containers supports **http1** (default) and **http2** (`h2c`). Use HTTP/2 if your container application is configured to listen for HTTP/2 requests, such as a **gRPC** service or a web server that uses HTTP/2 features like multiplexing, otherwise, HTTP/1 is recommended.
+Serverless Containers supports **http1** (default) and **http2** (`h2c`). Use HTTP/2 if your container application is configured to listen for HTTP/2 requests, such as a **gRPC** service or a web server that uses HTTP/2 features like multiplexing, otherwise, HTTP/1 is recommended.