Skip to content

chore: fix some minor issues in the comments #13495

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nuxtreact wants to merge 1 commit into
base: master
Choose a base branch
from
+3 −3
Open

chore: fix some minor issues in the comments #13495

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion api/v2api/full.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ type FullNode interface {
// the blockchain.
//
// <b>Note: This API is experimental and may change as we explore the
// appropriate design for the Filecoin v2 APIs.<b/>
// appropriate design for the Filecoin v2 APIs.</b>
//
// Please see Filecoin V2 API design documentation for more details:
// - https://www.notion.so/filecoindev/Lotus-F3-aware-APIs-1cfdc41950c180ae97fef580e79427d5
Expand Down
4 changes: 2 additions & 2 deletions documentation/en/api-experimental-user-facing-v2-docs/CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,13 +8,13 @@ This directory contains the experimental user-facing documentation for Filecoin'
- This documentation describes experimental V2 APIs that are subject to change

## Workflow
1. (If this hasn't already been don) Copy updates from Notion into this repository
1. (If this hasn't already been done) Copy updates from Notion into this repository
2. Make changes, likely using Claude Code by pointing to local changes or changes in a PR.
2. Regenerate the table of contents if you've added or modified sections
3. Submit changes for team review via pull request
4. After approval, publish updated content back to Notion

**Important**: Always regenerate the table of contents before committing changes to ensure it accurately reflects the document structure. The table of contents is comprehensive and includes all sections of the document, helping readers navigate the content. It also helps give an overview in the diff of what content is being added/changed and where in the document.
**Important**: Always regenerate the table of contents before committing changes to ensure it accurately reflects the document structure. The table of contents is comprehensive and includes all sections of the document, helping readers navigate the content. It also helps give an overview in the diff of what content is being added/changed and where in the document.

## Key Files
- `api-v2-experimental.md`: The main user facing documentation file that is copied to Notion.
Expand Down
Loading