docs: drop redundant Caddyfile/Dockerfile filename comments

Per review feedback, a bare `# Caddyfile` or `# Dockerfile` on the first
line of a `caddyfile` or `dockerfile` fenced block restates information
the language tag already carries and just adds noise. Remove those
generic headers and keep only the comments that name a specific file
(e.g. `# compose.yaml`, `# static-build.Dockerfile`, `// public/index.php`)
or describe the block's purpose.

Author: dunglas

docs/config.md

@@ -14,7 +14,6 @@ You can specify a custom path with the `-c` or `--config` option.
 A minimal `Caddyfile` to serve a PHP application is shown below:
 
 ```caddyfile
-# Caddyfile
 # The hostname to respond to
 localhost
 
@@ -45,7 +44,6 @@ PHP:
 - You should copy an official template provided by the PHP project:
 
 ```dockerfile
-# Dockerfile
 FROM dunglas/frankenphp
 
 # Production:
@@ -87,7 +85,6 @@ The `php_server` or the `php` [HTTP directives](https://caddyserver.com/docs/cad
 Minimal example:
 
 ```caddyfile
-# Caddyfile
 localhost {
 	# Enable compression (optional)
 	encode zstd br gzip
@@ -99,7 +96,6 @@ localhost {
 You can also explicitly configure FrankenPHP using the [global option](https://caddyserver.com/docs/caddyfile/concepts#global-options) `frankenphp`:
 
 ```caddyfile
-# Caddyfile
 {
 	frankenphp {
 		num_threads <num_threads> # Sets the number of PHP threads to start. Default: 2x the number of available CPUs.
@@ -125,7 +121,6 @@ You can also explicitly configure FrankenPHP using the [global option](https://c
 Alternatively, you may use the one-line short form of the `worker` option:
 
 ```caddyfile
-# Caddyfile
 {
 	frankenphp {
 		worker <file> <num>
@@ -138,7 +133,6 @@ Alternatively, you may use the one-line short form of the `worker` option:
 You can also define multiple workers if you serve multiple apps on the same server:
 
 ```caddyfile
-# Caddyfile
 app.example.com {
     root /path/to/app/public
 	php_server {
@@ -166,7 +160,6 @@ it's a PHP file or not. Read more about it in the [performance page](performance
 Using the `php_server` directive is equivalent to this configuration:
 
 ```caddyfile
-# Caddyfile
 route {
 	# Add trailing slash for directory requests
 	@canonicalPath {
@@ -190,7 +183,6 @@ route {
 The `php_server` and the `php` directives have the following options:
 
 ```caddyfile
-# Caddyfile
 php_server [<matcher>] {
 	root <directory> # Sets the root folder to the site. Default: `root` directive.
 	split_path <delim...> # Sets the substrings for splitting the URI into two parts. The first matching substring will be used to split the "path info" from the path. The first piece is suffixed with the matching substring and will be assumed as the actual resource (CGI script) name. The second piece will be set to PATH_INFO for the script to use. Default: `.php`
@@ -218,7 +210,6 @@ Workers can instead be restarted on file changes via the `watch` directive.
 This is useful for development environments.
 
 ```caddyfile
-# Caddyfile
 {
 	frankenphp {
 		worker {
@@ -237,7 +228,6 @@ where the FrankenPHP process was started. You can instead also specify one or mo
 [shell filename pattern](https://pkg.go.dev/path/filepath#Match):
 
 ```caddyfile
-# Caddyfile
 {
 	frankenphp {
 		worker {
@@ -269,7 +259,6 @@ The following example will always serve a file in the public directory if presen
 and otherwise forward the request to the worker matching the path pattern.
 
 ```caddyfile
-# Caddyfile
 {
 	frankenphp {
 		php_server {
@@ -294,7 +283,6 @@ But when the fix depends on a third party you don't control,
 `max_requests` provides a pragmatic and hopefully temporary workaround for production:
 
 ```caddyfile
-# Caddyfile
 {
 	frankenphp {
 		max_requests 500
@@ -324,7 +312,6 @@ When set, PHP will load all the file with the `.ini` extension present in the gi
 You can also change the PHP configuration using the `php_ini` directive in the `Caddyfile`:
 
 ```caddyfile
-# Caddyfile
 {
     frankenphp {
         php_ini memory_limit 256M
@@ -356,7 +343,6 @@ has been read. (for example: [Mercure](mercure.md), WebSocket, Server-Sent Event
 This is an opt-in configuration that needs to be added to the global options in the `Caddyfile`:
 
 ```caddyfile
-# Caddyfile
 {
   servers {
     enable_full_duplex

docs/docker.md

@@ -23,7 +23,6 @@ The tags follow this pattern: `dunglas/frankenphp:<frankenphp-version>-php<php-v
 Create a `Dockerfile` in your project:
 
 ```dockerfile
-# Dockerfile
 FROM dunglas/frankenphp
 
 COPY . /app/public
@@ -47,7 +46,6 @@ The [`docker-php-extension-installer`](https://github.com/mlocati/docker-php-ext
 Adding additional PHP extensions is straightforward:
 
 ```dockerfile
-# Dockerfile
 FROM dunglas/frankenphp
 
 # add additional extensions here:
@@ -66,7 +64,6 @@ FrankenPHP is built on top of Caddy, and all [Caddy modules](https://caddyserver
 The easiest way to install custom Caddy modules is to use [xcaddy](https://github.com/caddyserver/xcaddy):
 
 ```dockerfile
-# Dockerfile
 FROM dunglas/frankenphp:builder AS builder
 
 # Copy xcaddy in the builder image
@@ -107,7 +104,6 @@ The `builder` image provided by FrankenPHP contains a compiled version of `libph
 Set the `FRANKENPHP_CONFIG` environment variable to start FrankenPHP with a worker script:
 
 ```dockerfile
-# Dockerfile
 FROM dunglas/frankenphp
 
 # ...
@@ -163,7 +159,6 @@ FrankenPHP can run as non-root user in Docker.
 Here is a sample `Dockerfile` doing this:
 
 ```dockerfile
-# Dockerfile
 FROM dunglas/frankenphp
 
 ARG USER=appuser
@@ -189,7 +184,6 @@ If you expose FrankenPHP on a non-privileged port (1024 and above), it's possibl
 the webserver as a non-root user, and without the need for any capability:
 
 ```dockerfile
-# Dockerfile
 FROM dunglas/frankenphp
 
 ARG USER=appuser
@@ -229,7 +223,6 @@ To further reduce the attack surface and size of your FrankenPHP Docker images,
 When adding additional PHP extensions, you will need an intermediate build stage:
 
 ```dockerfile
-# Dockerfile
 FROM dunglas/frankenphp AS builder
 
 # Add additional PHP extensions here

docs/migrate.md

@@ -46,7 +46,6 @@ server {
 Becomes a single `Caddyfile`:
 
 ```caddyfile
-# Caddyfile
 example.com {
     root /var/www/app/public
     php_server
@@ -62,7 +61,6 @@ Your existing `php.ini` works as-is. See [Configuration](config.md) for where to
 You can also set directives directly in the `Caddyfile`:
 
 ```caddyfile
-# Caddyfile
 {
     frankenphp {
         php_ini memory_limit 256M
@@ -82,7 +80,6 @@ In PHP-FPM, you tune `pm.max_children` to control the number of worker processes
 In FrankenPHP, the equivalent is `num_threads`:
 
 ```caddyfile
-# Caddyfile
 {
     frankenphp {
         num_threads 16
@@ -93,7 +90,6 @@ In FrankenPHP, the equivalent is `num_threads`:
 By default, FrankenPHP starts 2 threads per CPU. For dynamic scaling similar to PHP-FPM's `pm = dynamic`:
 
 ```caddyfile
-# Caddyfile
 {
     frankenphp {
         num_threads 4
@@ -161,7 +157,6 @@ In [classic mode](classic.md), FrankenPHP works like PHP-FPM: each request boots
 For better performance, you can switch to [worker mode](worker.md), which boots your application once and keeps it in memory:
 
 ```caddyfile
-# Caddyfile
 example.com {
     root /var/www/app/public
     php_server {

docs/production.md

@@ -16,7 +16,6 @@ If you're using API Platform (which also uses FrankenPHP), refer to [the deploym
 First, create a `Dockerfile` in the root directory of your PHP project:
 
 ```dockerfile
-# Dockerfile
 FROM dunglas/frankenphp
 
 # Be sure to replace "your-domain-name.example.com" by your domain name
@@ -151,7 +150,6 @@ you must configure the [`trusted_proxies` global option](https://caddyserver.com
 so that Caddy trusts incoming `X-Forwarded-*` headers:
 
 ```caddyfile
-# Caddyfile
 {
 	servers {
 		trusted_proxies static <your-IPs>

docs/symfony.md

@@ -71,7 +71,6 @@ Hot reloading is enabled by default in [Symfony Docker](https://github.com/dungl
 To use the [hot reload](hot-reload.md) feature without Symfony Docker, enable [Mercure](mercure.md) and add the `hot_reload` sub-directive to the `php_server` directive in your `Caddyfile`:
 
 ```caddyfile
-# Caddyfile
 localhost
 
 mercure {

docs/wordpress.md

@@ -23,7 +23,6 @@ Run [WordPress](https://wordpress.org/) with FrankenPHP to enjoy a modern, high-
 For a production-ready setup, prefer using `frankenphp run` with a `Caddyfile` like this one:
 
 ```caddyfile
-# Caddyfile
 example.com
 
 php_server
@@ -36,7 +35,6 @@ log
 To use the [hot reload](hot-reload.md) feature with WordPress, enable [Mercure](mercure.md) and add the `hot_reload` sub-directive to the `php_server` directive in your `Caddyfile`:
 
 ```caddyfile
-# Caddyfile
 localhost
 
 mercure {