Update OpenClaw LP1 timezone guidance

Author: odinshen-git

content/learning-paths/laptops-and-desktops/openclaw_continuum/2_dgx_deploy.md

@@ -203,6 +203,14 @@ OPENCLAW_CRON_CHAT_IDS=<your-telegram-chat-id>
 OPENCLAW_GATEWAY_TOKEN=<generated-random-token>
 ```
 
+Set `OPENCLAW_CRON_TIMEZONE` to your local [IANA timezone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). Scheduled jobs use UTC when this setting is omitted:
+
+```text
+OPENCLAW_CRON_TIMEZONE=<your-IANA-timezone>
+```
+
+For example, use `Europe/London`, `America/New_York`, or `Asia/Singapore`. Weather questions in this Learning Path name their location explicitly, so you do not need to configure `OPENCLAW_DEFAULT_WEATHER_LOCATION`.
+
 {{% notice Note %}}
 Do not share your Telegram bot token or chat ID with anyone, and do not include them in screenshots, logs, or public repositories.
 {{% /notice %}}
@@ -351,16 +359,14 @@ OPENCLAW_QDRANT_BASE_URL=http://127.0.0.1:6333 \
 PYTHONPATH=app python3 -m unittest discover -s tests
 ```
 
-The output should look similar to:
+The output contains progress dots followed by this result:
 
 ```output
-............................................................................................................
-----------------------------------------------------------------------
-Ran 119 tests in 3.213s
-
 OK
 ```
 
+The number of tests and the elapsed time can change as the repository evolves. `OK` confirms that the complete suite passed.
+
 These tests validate command routing, task dispatch, cron parsing, ingestion helpers, and failure handling. They are software behavior tests, not hardware benchmarks.
 
 ## What you've learned and what's next

content/learning-paths/laptops-and-desktops/openclaw_continuum/5_cpu_only.md

@@ -200,10 +200,13 @@ OPENCLAW_TELEGRAM_BOT_TOKEN=<your-telegram-bot-token>
 OPENCLAW_TELEGRAM_ALLOWED_CHAT_IDS=<first-chat-id>,<second-chat-id>
 OPENCLAW_CRON_CHAT_IDS=<first-chat-id>,<second-chat-id>
 OPENCLAW_GATEWAY_TOKEN=<generated-random-token>
+OPENCLAW_CRON_TIMEZONE=<your-IANA-timezone>
 ```
 
 Separate multiple allowlisted chat IDs with commas. Both household members can then use the same bot and shared local collections.
 
+Use the same IANA timezone convention as the DGX Spark deployment. Scheduled jobs use UTC when this setting is omitted.
+
 Confirm the inference settings:
 
 ```text