Update sophos-central-source.md

[keyur-sumo]

Purpose of this pull request

This pull request (PR) ...

Issue number:

Select the type of change:

• Minor Changes - Typos, formatting, slight revisions
• Update Content - Revisions and updating sections
• New Content - New features, sections, pages, tutorials
• Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

[jpipkin1]

@kimsauce, when I ran yarn to preview this PR, it gave me raw-loader errors:

Module not found: Error: Can't resolve 'raw-loader' in '/Users/jpipkin/Documents/GitHub/forks/keyur-sumo/sumologic-documentation/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework'
Module not found: Error: Can't resolve 'raw-loader' in '/Users/jpipkin/Documents/GitHub/forks/keyur-sumo/sumologic-documentation/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework'
Module not found: Error: Can't resolve 'raw-loader' in '/Users/jpipkin/Documents/GitHub/forks/keyur-sumo/sumologic-documentation/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework'
Module not found: Error: Can't resolve 'raw-loader' in '/Users/jpipkin/Documents/GitHub/forks/keyur-sumo/sumologic-documentation/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework'
client (webpack 5.80.0) compiled with 4 errors

I had to run yarn add raw-loader so I could successfully do a local build for the patch-3 branch.

How should we handle these situations when they come up? Should we just go ahead and commit the updated yarn.lock file that results from running yarn add raw-loader? Or should we tell the PR submitter to run yarn install (and would that fix it)?

[JV0812]

@jpipkin1 This error is due to the addition of new components in our new C2C source. Before building you can just run the below command to instal the packages related to raw-loader.
yarn add raw-loader

[JV0812]

Minor fix

[keyur-sumo]

@JV0812 fix is made. can you please re-review?

[JV0812]

LGTM