Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
2 more typo fixes
  • Loading branch information
donald-pinckney committed Mar 3, 2026
commit 69798c064849f234b9d0bd5134cb4381c25b011f
2 changes: 1 addition & 1 deletion references/core/ai-patterns.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Temporal provides durable execution for AI/LLM applications, handling retries, r

For Python-specific implementation details and code examples, see `references/python/ai-patterns.md`. Temporal's Python SDK also provides pre-built integrations with several LLM and agent SDKs, which can be leveraged to create agentic workflows with minimal effort (when working in Python).

The remainder of this document describes general principles to follow when building AI/LLM applications in Temporal, particularly when from scratch instead of with an integration.
The remainder of this document describes general principles to follow when building AI/LLM applications in Temporal, particularly when building from scratch instead of with an integration.

## Why Temporal for AI?

Expand Down
2 changes: 1 addition & 1 deletion references/core/determinism.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ Result: Commands don't match history → NondeterminismError

## **Central Concept**: Place Non-Determinism within Activities

In Temporal, activities are the primary mechanism for making non-deterministic code durable and peristed in workflow history. Generally speaking, you should place sources of non-determinism in activities, which provides durability and recording of results, as well as automated retries and more. See `references/{your_language}/{your_language}.md` for the language you are working in for how to do this in practice.
In Temporal, activities are the primary mechanism for making non-deterministic code durable and persisted in workflow history. Generally speaking, you should place sources of non-determinism in activities, which provides durability and recording of results, as well as automated retries and more. See `references/{your_language}/{your_language}.md` for the language you are working in for how to do this in practice.

For a few simple cases, like timestamps, random values, UUIDs, etc. the Temporal SDK in your language may provide durable variants that are simple to use. See `references/{your_language}/determinism.md` for the language you are working in for more info.

Expand Down