fix(serverless): faq title level (#3901)

* fix(serverless): faq title level

* one more

Author: thomas-tacquet

faq/serverless-containers.mdx

@@ -97,11 +97,11 @@ Ensure that your code avoids heavy computations or long-running initialization a
 
 Refer to our dedicated page about [Serverless Containers limitations and configuration restrictions](/serverless/containers/reference-content/containers-limitations/) for more information.
 
-# Where should I host my container images for deployment ?
+## Where should I host my container images for deployment ?
 
 <Macro id="container-registry-note" />
 
-# How can I copy an image from an external registry to Scaleway Container Registry?
+## How can I copy an image from an external registry to Scaleway Container Registry?
 
 You can copy an image from an external registry by [logging in to the Scaleway Container Registry](/containers/container-registry/how-to/connect-docker-cli/) using the Docker CLI, and by copying the image as shown below:
 
@@ -153,7 +153,7 @@ Scaleway Serverless Containers do not currently support attaching block storage.
 stateless, meaning they do not retain data between invocations. For persistent storage, we recommend using external
 solutions like Scaleway Object Storage.
 
-# Why does my container have an instance running after deployment, even with min-scale 0?
+## Why does my container have an instance running after deployment, even with min-scale 0?
 
 Currently, a new container instance will always start after each deployment, even if there is no traffic and the minimum
 scale is set to 0. This behavior is not configurable at this time.

faq/serverless-functions.mdx

@@ -180,7 +180,7 @@ Scaleway Serverless Functions do not currently support attaching block storage.
 stateless, meaning they do not retain data between invocations. For persistent storage, we recommend using external
 solutions like Scaleway Object Storage.
 
-# Why does my function have an instance running after deployment, even with min-scale 0?
+## Why does my function have an instance running after deployment, even with min-scale 0?
 
 Currently, a new function instance will always start after each deployment, even if there is no traffic and the minimum
 scale is set to 0. This behavior is not configurable at this time.

faq/serverless-jobs.mdx

@@ -94,11 +94,11 @@ Scaleway Serverless Jobs is part of the Scaleway ecosystem, it can therefore be
 
 When starting a job, you can use contextual options to define the number of jobs to execute at the same time. Refer to the [dedicated documentation](/serverless/jobs/how-to/run-job/#how-to-run-a-job-with-contextual-options) for more information.
 
-# Where should I host my jobs images for deployment ?
+## Where should I host my jobs images for deployment ?
 
 <Macro id="container-registry-note" />
 
-# How can I copy an image from an external registry to Scaleway Container Registry?
+## How can I copy an image from an external registry to Scaleway Container Registry?
 
 You can copy an image from an external registry by [logging in to the Scaleway Container Registry](/containers/container-registry/how-to/connect-docker-cli/) using the Docker CLI, and by copying the image as shown below:
 
@@ -119,4 +119,4 @@ skopeo copy --override-os linux docker://docker.io/alpine:latest docker://rg.fr-
 
 Scaleway Serverless Jobs does not currently support Scaleway VPC or Private Networks, though this feature is under development.
 
-To add network restrictions on your resource, consult the [list of prefixes used at Scaleway](https://www.scaleway.com/en/peering/). Serverless resources do not have dedicated or predictable IP addresses.
+To add network restrictions on your resource, consult the [list of prefixes used at Scaleway](https://www.scaleway.com/en/peering/). Serverless resources do not have dedicated or predictable IP addresses.