[Doc] The introductions of EventMesh Connector and EventMesh Storage are incorrect

[pandaapo]

(Related issue apache/eventmesh#4680. CC @VishalMCF.)

https://github.com/apache/eventmesh-site/blob/master/docs/instruction/03-runtime.md

Current EventMesh Connector is different from the initial EventMesh Connector, and it is a standalone service now. The initial EventMesh Connector was later changed to EventMesh Storage, but the relevant instructions in the documentation were not changed, resulting in users not knowing how to use Storage and Connector, and even attempting to use Storage or Connector in the wrong way.
For example:

The content of the file is the mapping from the plugin instance name to the plugin instance, see eventmesh-connector-rocketmq plugin module for details.

implementation project(":eventmesh-connectors:eventmesh-connector-rocketmq")

#connector plugin
eventMesh.connector.plugin.type=rocketmq

// Example: Load the RocketMQ plugin
implementation project(":eventmesh-connectors:eventmesh-connector-rocketmq")

Now eventmesh-connector-rocketmq as Connector, it does not run as a plugin, here they should be eventmesh-storage-rocketmq.

Additionally, all of the image paths in this document are incorrect. They should be /static/images/... instead of /images/... (Similar issue: #142 ).

[Whitegabriella789]

May I help with this issue? I am a bit new to GitHub but have taken some courses on it if that's ok. However, I'm not new to writing up documentation.

[VishalMCF]

Sure go ahead

…

On Wed, 3 Jul 2024 at 07:24, Whitegabriella789 ***@***.***> wrote: May I help with this issue? I am a bit new to GitHub but have taken some courses on it if that's ok. However, I'm not new to writing up documentation. — Reply to this email directly, view it on GitHub <#159 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQYCBCXKVLCA7LMUUTY6C73ZKNKVBAVCNFSM6AAAAABKITIITGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBUHA4DMNJSGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>