Skip to content

Conversation

NeuroShepherd
Copy link
Member

No description provided.

@NeuroShepherd
Copy link
Member Author

NeuroShepherd commented Mar 25, 2025

@MalikaIhle I saw you were making some typo fixes on main. I've moved those edits over to this pull request, and you can keep making edits to this branch with the following steps:

git checkout main
git pull
git fetch
git checkout malikas_typos

^ This will grab the branch and check it out on your computer. You can then add more typo corrections to this PR with the typical git add git commit and git push steps.

@MalikaIhle
Copy link
Member

I was fixing them on github directly as I was reading. I had not cloned this repo locally.

@MalikaIhle
Copy link
Member

isn't that what we are expecting readers of our tutorials to do by clicking on 'edit this page' ? (though I suppose for them it would fork and create a pull request, right?)

@NeuroShepherd
Copy link
Member Author

NeuroShepherd commented Mar 25, 2025

isn't that what we are expecting readers of our tutorials to do by clicking on 'edit this page' ? (though I suppose for them it would fork and create a pull request, right?)

You are only able to make edits directly onto the main branch because you're an admin, but other readers won't have the rights to do that. They will have to open Pull Requests (but they don't have to fork.)

In either case, it is generally best to collect as many typos/changes like that as possible into a single PR.

@NeuroShepherd
Copy link
Member Author

More generally, I have a lot of additional changes that will happen to the manual content, many of which will overwrite the existing content. So I wouldn't spend much time on fixing small errors and typos quite yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants