Update docs to specify where PeerManager::process_events is called

[vss96]

Doc changes for #1075

[codecov]

Codecov Report

Merging #1082 (ac6bd64) into main (801d6e5) will decrease coverage by 0.01%.
The diff coverage is n/a.

❗ Current head ac6bd64 differs from pull request most recent head 2f0f0c9. Consider uploading reports for the commit 2f0f0c9 to get more accurate results

@@            Coverage Diff             @@
##             main    #1082      +/-   ##
==========================================
- Coverage   90.76%   90.74%   -0.02%     
==========================================
  Files          65       65              
  Lines       33894    33894              
==========================================
- Hits        30764    30758       -6     
- Misses       3130     3136       +6     

Impacted Files	Coverage Δ
lightning/src/ln/peer_handler.rs	45.94% <ø> (ø)
lightning/src/ln/functional_tests.rs	97.44% <0.00%> (-0.10%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 801d6e5...2f0f0c9. Read the comment docs.

[vss96]

@TheBlueMatt I hope this should be enough to update the docs?

[TheBlueMatt]

I think we should mention this call in lightning-net-tokio's three public methods that create connections, but this is fine either way.

[valentinewallace]

ACK mod squashing the fixup

[TheBlueMatt]

Can you squash the commits into one? Then happy to land this.

[vss96]

I squashed it into a single commit, but for some reason the check_commits stage is failing

[TheBlueMatt]

According to github, you now have four commits in the PR. See https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#squashing-commits for instructions on how to squash and force-push.

[vss96]

@valentinewallace I'm not sure how your changes got in when I pushed I could only see my changes in the diff.

[vss96]

@TheBlueMatt I managed to squash the commit by following the instructions that were given, but somehow i ended up with other file changes 😓

[TheBlueMatt]

Huh! I'm not entirely sure how that happened. In any case, I went ahead and took the previous version of this PR from yesterday, squashed the commit into one, and pushed it (github, by default, allows maintainers to push to your branches that are associated with a PR).

[vss96]

Thank you for the help! :)