diff --git a/profiles/local/local-light.yml b/profiles/local/local-light.yml
index 6a14351..6851b5d 100644
--- a/profiles/local/local-light.yml
+++ b/profiles/local/local-light.yml
@@ -2,7 +2,7 @@ id: local-light
 endpoint: https://inference.ai.rakestrawhome.com/v1
 model: "nvidia/Nemotron-3-Nano-30B-A3B"
 temperature: 0.15
-reasoning_effort: high
+reasoning_effort: medium
 top_p: 0.98
 timeout_seconds: 900
 api_key_env: OPENROUTER_API_KEY
diff --git a/prompts/pipeline-weather/tomorrow/tomorrow_generated_text.user.md b/prompts/pipeline-weather/tomorrow/tomorrow_generated_text.user.md
index 24edd75..c0176ef 100644
--- a/prompts/pipeline-weather/tomorrow/tomorrow_generated_text.user.md
+++ b/prompts/pipeline-weather/tomorrow/tomorrow_generated_text.user.md
@@ -21,7 +21,7 @@ The summary should typically consist of two sentences.
 
 If an active warning is relevant during the report period, lead with the hazard. Otherwise, the first sentence should state the most likely local weather outcome for the valid period, including the overall character of the weather and expected temperature/temperature range. 
 
-The second sentence should state the most important active hazard, caveat, uncertainty, or alternate outcome, if one exists. If there is no meaningful caveat, the second sentence may be omitted, or may briefly say that no major complications are apparent.
+The second sentence should state the most important active hazard, caveat, uncertainty, or alternate outcome, if one exists. If there is no meaningful caveat, the second sentence may be omitted.
 
 In the lead, distinguish the main weather outcome from the caveat. If showers and thunderstorms have different timing, state that difference rather than combining them as a single risk throughout the valid period. If the main caveat is a regional severe-weather or precipitation risk displaced from the report location, state that limitation clearly.