Typo in Documentation - do I need to fork to change

There is a typo in the documentation and I really don’t want to fork it just for this

837 TCP Rsync Remote synchronization Optional Closed

Should be

873 TCP Rsync Remote synchronization Optional Closed

The 3 & 7 are transposed

On the documentation page, right side, is a “Feedback” button. Simply use it and report the issue. (I overlooked the button initially too a while back… just was not looking at the side for contact information.)

I thought about reporting it for you, but it is good experience. Or if you request, I can report it.

1 Like

Thanks for the issue report @Alister.

In future instances if you notice a small typo like this, you can also use the Edit page button at the top of the article to go directly to the Github web UI file editor.


From there you can make your edits and submit a PR without ever having to go through the manual work of creating a fork and so on.

When I click the edit page I get the above message rather than the GUI editor

This why I asked the question

If I search on the github repo for the file DefaultPorts.md, then click on the file - I get to the GUI editor - but the code is read only

I got to the editor and trying to make a PR throws up

You’re trying to make changes in a project you don’t have write access to.

Do you want to create a fork of this project to commit your proposed changes to?

looking at the number of forks 193 - it looks like that’s what I have to do

Ah I see. I hadn’t experienced that since I have edit access. I’ll look into it but it looks like that might be expected behavior.

1 Like