[Minor] Documentation mentions "Structured JSON" instead of "Nested JSON"

[Martin_Chrastek]

The documentation mentions “structured JSON” in several places like Quick Start Guide on JSON, JSON File Format and so on. I believe that the more proper term would be “nested JSON” instead as there is no set “structure” per se, but that feature only allows the user to upload nested JSON files.
Also, this would be backed up by the way how other TMS companies use this term, for example:

• Lokalise’s Structured JSON docs page says: “Keep in mind that structured JSON does not support key nesting (multi-level keys, such as nested JSON), so all of the keys must be provided in one level.”
• Transifex’s Structured JSON docs page is similiar to what Lokalise treats as “structured JSON” and as per their usual JSON docs page, you can use nesting right away
• Phrases’ Nested JSON docs page

[vaclav]

Thanks for the feedback. It’s a good point. We will consider to change it as soon as we are doing some major change to the documentation.