[BUG] - Inconsistency in the Deploy Nebari on local machines guide

Describe the bug

In the Deploy Nebari on local machines (for testing) guide of the documentation, it is clearly stated that:

🔥warning

Currently, Nebari does not support local mode on Windows and macOS.

However, there is a tip in the Initializing Nebari section with the following information:

💡tip

The main temp folder on a MacOS system can be found by inspecting the value of $TMPDIR. This folder and its files are not meant to be user-facing and will present you with a seemingly random directory path similar to /var/folders/xx/xxxxx/T

I believe this comes from other How-to Guides (e.g., Deploy Nebari on AWS) but should not be in this particular guide.

Expected behavior

If macOS is not supported for local deployments, I don't see the relevance of having a tip refering to the temp folder in macOS.

How to Reproduce the problem?

Go to the Initializing Nebari of the Deploy Nebari on local machines (for testing) guide. This can found here in the source code.

Command output

No response

Versions and dependencies used.

No response

Anything else?

No response

Open docs/docs/how-tos/nebari-local.md and inspect the Initializing Nebari section around lines 83–87. Align the macOS temp-folder tip with the guide’s stated platform support, then verify the rendered guide no longer contains conflicting guidance.