Reading comprehension: How do you understand this extract from an API documentation?

Not sure whether this belongs here, but I was reading the following section from a documentation and when looking to other resources, I noticed that I misunderstood it. I'm wondering whether it's me or this is really linguistically ambiguous. How do you understand the following text:

If this option is specified, the remaining arguments are scanned, and all arguments that are enclosed between a pair of '@@' arguments are interpreted as file paths, exported in the document store, and passed to the command in the form of the resulting document path. Arguments between "@@u" and "@@" are considered URIs, and any "file:" URIs are exported. The exports are non-persistent and with read and write permissions for the application.

So, according to this section, how should I correctly write the arguments?

1. @@path1@@ @@path2@@ ...
2. @@ path1 path2 @@