Copyedit 'Event Source Connector' pattern

[fifthposition]

Description

50 (PR #39)

In the seo description text, I've tried to be consistent with the first pattern I worked on, the Event Source pattern. Let me know if we want to format the description another way--just want to make sure that all patterns are consistent. :-)

New Pattern Checklist

• [ ] Pattern file name should follow docs/pattern-category/pattern-name.md
• [ ] Create an on-brand diagram (https://docs.google.com/presentation/d/1Zf256Z6fBvre3uclIbmxXsDpnTIxiBX66b13pHbGIYc/edit?usp=sharing)
• [ ] Implement ksqlDB or code example (not all patterns will have code, but highly desired)
• [ ] Provide references
• [ ] Validate hyperlinks
• [ ] Spell check (e.g. using aspell)

[ybyzek]

@fifthposition please note GH is flagging a merge conflict -- can you please resolve and then we can approve?

[rspurgeon]

@fifthposition @ybyzek I merged main to resolve merge conflicts, please verify

[rspurgeon]

I reverted my attempt to merge in main here. We'll need to rebase or be careful about resolving the various merge conflicts I encountered. Sorry for the nose here...

[ybyzek]

@fifthposition as mentioned in Slack, we are closing PRs that show a GitHub conflict because we want to derisk launch and move quickly. New PRs will need to be opened.