[Documentation] s3 URI example uses my_key ambiguously

[yazad3]

Problem description

Documentation uses my_key ambiguously. In s3://my_key:my_secret@my_bucket/my_key, I think the first my_key in the 2 below examples in the ACCESS_KEY while the second my_key refers to the key in the bucket.

Another example of this ambiguity is s3://my_key:my_secret@my_server:my_port@my_bucket/my_key.

Steps/code to reproduce the problem

No issue to reproduce, just a documentation.

Versions

NA, but refering to the latest documentation in version 7.0.4 of smart_open.

Checklist

Before you create the issue, please make sure you have:

• Described the problem clearly
• Provided a minimal reproducible example, including any required data
• Provided the version numbers of the relevant software