Skip to content

Commit 9fae382

Browse files
authored
Apply suggestions from code review
1 parent 3a3441c commit 9fae382

1 file changed

Lines changed: 1 addition & 2 deletions

File tree

docs/source/en/modular_diffusers/write_own_pipeline_block.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,11 +17,10 @@ In Modular Diffusers, you build your workflow using `ModularPipelineBlocks`. We
1717
In this tutorial, we will focus on how to write a basic `PipelineBlock` and how it interacts with other components in the system. We will also cover how to connect them together using the multi-blocks: `SequentialPipelineBlocks`, `LoopSequentialPipelineBlocks`, and `AutoPipelineBlocks`.
1818

1919

20-
## Understanding the Foundation: `PipelineState`
20+
### Understanding the Foundation: `PipelineState`
2121

2222
Before we dive into creating `PipelineBlock`s, we need to have a basic understanding of `PipelineState` - the core data structure that all blocks operate on. This concept is fundamental to understanding how blocks interact with each other and the pipeline system.
2323

24-
## `PipelineState`
2524

2625
In the modular diffusers system, `PipelineState` acts as the global state container that `PipelineBlock`s operate on - each block gets a local view (`BlockState`) of the relevant variables it needs from `PipelineState`, performs its operations, and then updates `PipelineState` with any changes.
2726

0 commit comments

Comments
 (0)