docs: php intelliphense config

Author: abose

docs/07-Code Intelligence/02-php.md

@@ -31,7 +31,7 @@ The free version of Intelephense covers everything described above. If you own a
 
 PHP code intelligence only knows about the PHP files it can see. If your project is a WordPress theme or plugin (or any codebase that leans on functions/constants defined by a framework you don't have locally, like `get_header()`), those calls show up as **"Undefined function"** errors in the [Problems panel](/docs/Features/Problems%20Panel/ESLint) even though the code is correct.
 
-Fix this by dropping an `intelephense.config.json` file in your project root, then restart Phoenix Code so PHP code intelligence picks it up.
+Fix this by dropping an `intelephense.config.json` file in your project root, then restart Phoenix Code (or switch between projects) so PHP code intelligence picks it up.
 
 **Recommended: point it at the framework's stub files** so the functions are actually recognized (you get real hover info and completions, not just silence):
 
@@ -43,7 +43,15 @@ Fix this by dropping an `intelephense.config.json` file in your project root, th
 }
 ```
 
-Install the stubs with Composer first, e.g. `composer require --dev php-stubs/wordpress-stubs` for WordPress. Similar stub packages exist for WooCommerce, Laravel, and other frameworks.
+Install the stubs with Composer first. Open **View > Terminal** for a terminal already rooted at your project (same steps on Windows, macOS, and Linux), then run:
+
+```bash
+composer require --dev php-stubs/wordpress-stubs
+```
+
+> Needs [Composer](https://getcomposer.org/download/) installed. If the command isn't found, install Composer first (its site has steps for Windows, macOS, and Linux).
+
+Similar stub packages exist for WooCommerce, Laravel, and other frameworks.
 
 > Composer puts the stubs inside your project (`vendor/…`), so the path above works as-is on Windows, macOS, and Linux. Pointing `includePaths` at your actual local WordPress install instead would work too, but the path is different for every setup (XAMPP, MAMP, Local, Docker, …) and you'd have to track it down yourself — the stub package sidesteps that entirely.
 
@@ -57,7 +65,9 @@ Install the stubs with Composer first, e.g. `composer require --dev php-stubs/wo
 }
 ```
 
-> Commit `intelephense.config.json` to your repo so the whole team gets the same settings. See the [configuration reference](https://intelephense.com/docs) for the full list of `diagnostics` and `environment` options.
+> This only silences the error. Code intelligence still doesn't know what these functions are, so you won't get hover docs or autocomplete for them — use the stub option above for that.
+
+Commit `intelephense.config.json` to your repo so the whole team gets the same settings. See the [configuration reference](https://intelephense.com/docs) for the full list of `diagnostics` and `environment` options.
 
 ## Running PHP Pages