diff --git a/src/_posts/platform/app/2000-01-01-procfile.md b/src/_posts/platform/app/2000-01-01-procfile.md
index 54e38e3ee..e1dbfbce8 100644
--- a/src/_posts/platform/app/2000-01-01-procfile.md
+++ b/src/_posts/platform/app/2000-01-01-procfile.md
@@ -2,7 +2,7 @@
 index: 11
 title: Procfile
 tags: internals process types procfile heroku
-modified_at: 2026-04-29 00:00:00
+modified_at: 2026-07-16 00:00:00
 ---
 
 Procfile support is one of our
@@ -130,9 +130,10 @@ with the following format:
 ```
 
 - `<process_type>` designates the name of the process type. It can only contain
-  alphanumerics (`[A-Za-z0-9]+`). Except this rule, you are free to name your
-  process type how you want: `heavyProcess`, `synchronizer`, `scheduler`,
-  `console`, `trex`... These are all examples of valid process type names.
+  alphanumerics (`[A-Za-z0-9]+`) and must be no longer than 24 characters.
+  Except these two rules, you are free to name your process type how you want:
+  `heavyProcess`, `synchronizer`, `scheduler`, `console`, `trex`... These are
+  all examples of valid process type names.
 - `<command>` designates the command to run when a container of the specified
   type is booted up. It can be any Bash command. Using environment variables in
   the command is allowed, and even encouraged.