Correct the PHP-FPM process-model wording in the docs

[sascha-egerer]

No description provided.

[Copilot]

Pull request overview

Updates documentation to accurately describe PHP-FPM’s request lifecycle (pooled/reused worker processes, but per-request teardown of PHP userland state), clarifying why in-memory storage resets each request and preventing a common misunderstanding about “new process per request”.

Changes:

• Reworded PHP-FPM behavior in the InMemoryCache storage characteristics to reflect userland state teardown rather than “new process”.
• Expanded the FAQ explanation to precisely describe pooled workers + per-request state reset.
• Adjusted the portable-config guidance to use the same accurate PHP-FPM wording.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
docs/features/storage.md	Corrects the PHP-FPM explanation for why InMemoryCache resets each request.
docs/faq.md	Clarifies PHP-FPM pooling vs per-request userland teardown in the production warning for InMemoryCache.
docs/advanced/portable-config.md	Aligns PHP-FPM wording to accurately explain why configs are rebuilt per request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.