Update FAQ on filesystem and application branches (#1962)

* Update FAQ on filesystem and application branches

Clarified filesystem changes and application linking.

* Fix sentence and H-levels

---------

Co-authored-by: sushmangupta <[email protected]>
Co-authored-by: Su <[email protected]>

Author: TrayserCassa

products/paas/shopware/faq.md

@@ -4,45 +4,46 @@ nav:
   position: 50
 ---
 
-## Frequently Asked Questions
+# Frequently Asked Questions
 
-### Can I roll back my deployment if I lose my git history?
+## Can I roll back my deployment if I lose my git history?
 
 For now, no rollback is possible when you do a force push and lose your git history
 
-### Is it possible to write to the local filesystem?
+## Is it possible to write to the local filesystem?
 
 No, all containers are stateless, and local file writes are discouraged. Persistent storage must use S3 buckets or other external storage solutions.
+Changes to the filesystem and Shopware code must be made directly in the Git repository.
 
-### How can I connect my already deployed application to a new branch?
+## How can I connect my already deployed application to a new branch?
 
 The application that you create is linked to a commit SHA and not to a branch. You can change the existing application commit SHA by running `sw-paas application update`. What matters is the commit configured for a given application.
 
-### Can I run different applications like Node.js?
+## Can I run different applications like Node.js?
 
 No, currently PaaS is limited to Shopware projects.
 
-### How are secrets managed in PaaS?
+## How are secrets managed in PaaS?
 
 Secrets are stored in the PaaS secret store and can be applied at the organization, project, or application level. They are encrypted in the database and decrypted only when accessed via the CLI.
 
-### Can I access the database directly?
+## Can I access the database directly?
 
 Yes. Follow the guide on [databases](./resources/databases.md).
 
-### Can I customize the infrastructure (e.g., change web server configurations)?
+## Can I customize the infrastructure (e.g., change web server configurations)?
 
 No, the infrastructure is opinionated and pre-configured. Customizations at the server level are not allowed.
 
-### Are CDN or database configurations customizable?
+## Are CDN or database configurations customizable?
 
 No, PaaS uses Fastly as the CDN and provides a fixed database configuration at the moment. Customizations to these resources are currently under development.
 
-### Can I host my custom applications?
+## Can I host my custom applications?
 
 Custom applications and decoupled storefront hosting will be evaluated based on customer needs but are not currently supported.
 
-### What is the difference between `exec` and `command` ?
+## What is the difference between `exec` and `command` ?
 
 1. **Container Management**:
 
@@ -58,10 +59,10 @@ Custom applications and decoupled storefront hosting will be evaluated based on
    - `exec`: Best for debugging, maintenance, and interactive work
    - `command`: Best for automation, CI/CD, and scheduled tasks
 
-### Can I connect to my PaaS instance via SSH
+## Can I connect to my PaaS instance via SSH
 
 Yes, you can connect to your PaaS instance — but not via traditional SSH. Instead, we provide a remote terminal session through the `sw-paas exec` CLI command. This command allows you to execute shell commands inside your PaaS environment remotely, effectively giving you SSH-like access for troubleshooting, deployments, or interactive sessions.
 
-### Where can I see the status of my PaaS application update?
+## Where can I see the status of my PaaS application update?
 
 You can see the status of your PaaS application by running `sw-paas application list`. This command shows the current status of your application, including whether the update was successful or if it's still in progress. To monitor all real-time events associated with the project and its applications run `sw-paas watch` this provides a live stream of events and is especially useful for tracking the progress of an ongoing update.