From 52a1e1503820739e16668328024bf932fb8cc97d Mon Sep 17 00:00:00 2001 From: ZhenLiu94 Date: Wed, 27 Jan 2021 16:27:29 +0800 Subject: [PATCH] doc: Correct spelling mistakes. Signed-off-by: ZhenLiu94 --- doc/radosgw/pubsub-module.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/radosgw/pubsub-module.rst b/doc/radosgw/pubsub-module.rst index e2eaac7c8e2..36838a67237 100644 --- a/doc/radosgw/pubsub-module.rst +++ b/doc/radosgw/pubsub-module.rst @@ -208,7 +208,7 @@ To update a topic, use the same command used for topic creation, with the topic Request parameters: - push-endpoint: URI of an endpoint to send push notification to -- OpaqueData: opaque data is set in the topic configuration and added to all notifications triggered by the ropic +- OpaqueData: opaque data is set in the topic configuration and added to all notifications triggered by the topic The endpoint URI may include parameters depending with the type of endpoint: @@ -586,7 +586,7 @@ the events will have an S3-compatible record format (JSON): - s3.object.metadata: not supported (an extension to the S3 notification API) - s3.object.tags: not supported (an extension to the S3 notification API) - s3.eventId: unique ID of the event, that could be used for acking (an extension to the S3 notification API) -- s3.opaqueData: opaque data is set in the topic configuration and added to all notifications triggered by the ropic (an extension to the S3 notification API) +- s3.opaqueData: opaque data is set in the topic configuration and added to all notifications triggered by the topic (an extension to the S3 notification API) In case that the subscription was not created via a non S3-compatible notification, the events will have the following event format (JSON):