Skip to content

Commit 9b1fa16

Browse files
fix(docs): correct typos in comments and strings found during code review (#461)
Non-functional changes only: - Fixed minor spelling mistakes in comments - Corrected typos in user-facing strings - No variables, logic, or functional code was modified. Signed-off-by: Marcel Petrick <[email protected]>
1 parent e6548f1 commit 9b1fa16

File tree

4 files changed

+5
-5
lines changed

4 files changed

+5
-5
lines changed

custom-nodes/v3_migration.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -96,11 +96,11 @@ class Example(io.ComfyNode):
9696

9797
### Step 2: Convert INPUT_TYPES to define_schema
9898

99-
Node properites like node id, display name, category, etc. that were assigned in different places in code such as dictionaries and class properties are now kept together via the ```Schema``` class.
99+
Node properties like node id, display name, category, etc. that were assigned in different places in code such as dictionaries and class properties are now kept together via the ```Schema``` class.
100100

101101
The ```define_schema(cls)``` function is expected to return a ```Schema``` object in much the same way INPUT_TYPES(s) worked in V1.
102102

103-
Supported core Input/Output types are stored and documented in ```comfy_api/{version}``` in ```_io.py```, which is namespaced as ```io``` by default. Since Inputs/Outputs are defined by classes now instead of dictionaries or strings, custom types are supported by either definining your own class or using the helper function ```Custom``` in ```io```.
103+
Supported core Input/Output types are stored and documented in ```comfy_api/{version}``` in ```_io.py```, which is namespaced as ```io``` by default. Since Inputs/Outputs are defined by classes now instead of dictionaries or strings, custom types are supported by either defining your own class or using the helper function ```Custom``` in ```io```.
104104

105105
Custom types are elaborated on in a section further below.
106106

interface/settings/3d.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,4 +64,4 @@ Change the background color, which can also be adjusted in the canvas.
6464

6565
Hide or show the grid on initialization
6666

67-
![Show gird vs hide gird](/images/interface/setting/3d/hide_grid.jpg)
67+
![Show grid vs hide grid](/images/interface/setting/3d/hide_grid.jpg)

tutorials/image/cosmos/cosmos-predict2-t2i.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,5 +78,5 @@ Please follow the steps in the image to run the workflow:
7878
3. Ensure the `Load VAE` node has loaded `wan_2.1_vae.safetensors`
7979
4. Set the image size in `EmptySD3LatentImage`
8080
5. Modify the prompts in the `ClipTextEncode` node
81-
6. Click the `Run` button or use the shortcut `Ctrl(cmd) + Enter` to run the worklfow
81+
6. Click the `Run` button or use the shortcut `Ctrl(cmd) + Enter` to run the workflow
8282
7. Once generation is complete, the image will automatically save to the `ComfyUI/output/` directory. You can also preview it in the `save image` node. */}

tutorials/video/wan/wan2-2-animate.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ It can also replace characters in a video with animated characters, preserving t
3838
In this docs, we will provide two workflow:
3939

4040
1. Workflow that only uses core nodes (It is incomplete; you need to preprocess the image by yourself first)
41-
2. Workflow that inculdes some custom nodes (It is complete; you can use it directly, but some new user might not know how to install the custom nodes)
41+
2. Workflow that includes some custom nodes (It is complete; you can use it directly, but some new user might not know how to install the custom nodes)
4242

4343
## Wan2.2 Anmate ComfyUI native workflow(without custom nodes)
4444

0 commit comments

Comments
 (0)