Update user-code-deployment.adoc (#284)

Corrected the order in the footnotes accompanying the example code snippet --------- Co-authored-by: Rob Swain <[email protected]>
hazelcast · Jan 8, 2025 · 628ed5a · 628ed5a
1 parent 8bf6886
commit 628ed5a
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/docs/modules/ROOT/pages/user-code-deployment.adoc b/docs/modules/ROOT/pages/user-code-deployment.adoc
@@ -79,8 +79,8 @@ include::ROOT:example$/hazelcast-user-code-deployment-azure.yaml[]
 ----
 --
 ====
-<1> The bucket URI where backup data will be stored in
-<2> Name of the secret with credentials for accessing the Bucket URI.
+<1> Name of the secret with credentials for accessing the bucket URI 
+<2> URI of the bucket where backup data will be stored.
 
 == Configuring an External Data Store with Hazelcast Platform Operator
 
@@ -257,4 +257,4 @@ include::ROOT:example$/hazelcast-scheduled-executor-service.yaml[]
 
 == Configuring an Entry Processor with Hazelcast Platform Operator
 
-An entry processor executes your code on a map entry in an atomic way. To implement the `EntryProcessor` interface, you can deploy an `EntryProcessor` class from the Hazelcast Platform Operator to the classpath of a Hazelcast member. See xref:hazelcast:data-structures:entry-processor.adoc[Entry Processor] for more detailed information.
+An entry processor executes your code on a map entry in an atomic way. To implement the `EntryProcessor` interface, you can deploy an `EntryProcessor` class from the Hazelcast Platform Operator to the classpath of a Hazelcast member. See xref:hazelcast:data-structures:entry-processor.adoc[Entry Processor] for more detailed information.