I think it would be helpful to add a note that you might need to add execute permissions if you are using .sh scripts as part of the build sequence for Functions. This would have saved some time and a headache after getting a build error that wasn't very helpful. You can find my experience here . Basically, if you have a build.sh under the lib folder and the script doesn't have execute permission, then you'll get a JSON error.

I am following the instructions in the link below to delete a folder from one of my spaces: https://docs.digitalocean.com/products/spaces/how-to/use-folders/ The "..." More menu displayed in the last screenshot has been changed by "Actions", the written instructions reflect this but not the screenshot, it took me some time to work out why "..." wasn´t being displayed in my panel. Most times instead of reading everything people look at the picture to speed things up and the screenshot in the docs does not reflect what is currently visible. It would probably be useful for others if somebody could update that screenshot.

Documentation often gets out of date quickly. Allow the community to easily keep it up to date!

Currently creating a DNS record using doctl tool requires some guesswork from the user. What are the possible values for the "record-type" flag? How do I create a simple A or Host record? Seems like a very common and straightforward function. But neither the CLI help page for doctl nor the Docs page for it online provide the full syntax or example, including all possible values for various flags.

The latest instructions on connecting to managed MySQL with MySQL Workbench do not work.

So I'm super new to all this and trying to setup the very basics. Your documentation is not always up to date. For example just setting up doctl it has me try and create a Ubuntu 16.04 server which of course can't be done. And then even once I got a proper droplet setup, I can't log into it with doctl. I setup SSH keys but when I use the --ssh-key-path flag it jsut tells me I have the wrong format (even though it is normal formal from PuTTY gen.

Steps 6 & 8 are repeated in the Create Droplets section "Select additional options, like IPv6 and monitoring. These options come at no additional cost, and are easier to enable now than after creation."

the documentation for setting up an ingress controller with wildcard certificates has a number of places where file names are off. https://docs.digitalocean.com/tutorials/set-up-nginx-ingress-controller-to-use-wildcard-certificates/ for example kubectl get issuer letsencrypt-nginx-wcard -n backend should be kubectl get issuer letsencrypt-dev-wcard -n backend

There is little to no documentation on how to configure Redis on App Platform.

Please add C# code examples to https://docs.digitalocean.com/products/spaces/reference/s3-sdk-examples/