Skip to content

Commit 037f84f

Browse files
fix: Fix markdown list indentation in status_messages.md
Corrected nested list item indentation to use 2 spaces instead of 4-5 spaces to comply with MD007 markdown linting rules. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
1 parent f1defba commit 037f84f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

sources/platform/actors/development/programming_interface/status_messages.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -83,8 +83,8 @@ If your Actor has specific limitations for users on the Apify free plan (e.g., r
8383

8484
- Status messages: Use `Actor.setStatusMessage` or `Actor.exit` message to explain why a run finished early or failed (e.g., "Daily limit for free plan reached. Upgrade to continue.").
8585
- Provide clear error messages: Don't return generic system errors or fail the run in a way that looks like a platform issue. This frustrates users and makes troubleshooting difficult.
86-
- Wrong: API usage is limited to 10 results
87-
- Right: This Actor only allows up to 10 results for free users. Upgrade to a paid plan to receive unlimited results.
86+
- Wrong: API usage is limited to 10 results
87+
- Right: This Actor only allows up to 10 results for free users. Upgrade to a paid plan to receive unlimited results.
8888
- Documentation: Clearly state any limitations in your Actor's `README` and input schema descriptions so users know what to expect before running the Actor.
89-
- General restrictions (like limiting the number of results) must be explained in the top-level input schema description that renders above the input editor UI.
90-
- Feature-specific limitations must be included in the title of an input field. The title must include explanation in parenthesis such as `(paying users only)` or `(limited for free users)`. E.g. `Max comments (paying users only)`.
89+
- General restrictions (like limiting the number of results) must be explained in the top-level input schema description that renders above the input editor UI.
90+
- Feature-specific limitations must be included in the title of an input field. The title must include explanation in parenthesis such as `(paying users only)` or `(limited for free users)`. E.g. `Max comments (paying users only)`.

0 commit comments

Comments
 (0)