What steps does it take to reproduce the issue?
Go to https://guides.dataverse.org/en/6.7/api/native-api.html#imposing-a-limit-to-the-number-of-files-allowed-to-be-uploaded-to-a-dataset and scroll down to the curl commands.
There are two of these wrong-formatted sections here.
Which version of Dataverse are you using?
6.10.1
Any related open or closed issues to this bug report?
/
Screenshots:
No matter the issue, screenshots are always welcome.
To add a screenshot, please use one of the following formats and/or methods described here:
Are you thinking about creating a pull request for this issue?
Help is always welcome, is this bug something you or your organization plan to fix?
What steps does it take to reproduce the issue?
Go to https://guides.dataverse.org/en/6.7/api/native-api.html#imposing-a-limit-to-the-number-of-files-allowed-to-be-uploaded-to-a-dataset and scroll down to the curl commands.
When does this issue occur?
Whenever viewing this documentation page
Which page(s) does it occurs on?
https://guides.dataverse.org/en/6.7/api/native-api.html#imposing-a-limit-to-the-number-of-files-allowed-to-be-uploaded-to-a-dataset
What happens?
Some are nicely formatted in the greyed-out frame, but some are more like quotes or something.
To whom does it occur (all users, curators, superusers)?
All users
What did you expect to happen?
For e.g. curl -H “X-Dataverse-key:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx” -X DELETE “https://demo.dataverse.org/api/datasets/24/files/uploadlimit” to also be in the grey box like curl -H "X-Dataverse-key:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" -X POST "https://demo.dataverse.org/api/datasets/24/files/uploadlimit/500"" id is.
There are two of these wrong-formatted sections here.
Which version of Dataverse are you using?
6.10.1
Any related open or closed issues to this bug report?
/
Screenshots:
No matter the issue, screenshots are always welcome.
To add a screenshot, please use one of the following formats and/or methods described here:
Are you thinking about creating a pull request for this issue?
Help is always welcome, is this bug something you or your organization plan to fix?