[doc] Update instructions for different dimensions

howtos/different-dimensions-howto.md

@@ -20,16 +20,24 @@ The array of dimensions looks something like:
 
 Use the dimensions you wish (see the disclaimer below).
 
-##### 3. Recompile the code
+##### 3. Post-processing
+
+The (probably) only changes that need to be made in the postprocessing are in
+`cocopp.testbedsettings`. Search for the corresponding `Testbed` class (there
+is one per test suite, for example `GECCOBBOBTestbed` for the `bbob` test
+suite). In each `Testbed` class, there are variables that are related to the
+displayed dimensions. If you change these accordingly, it might run already
+"out of the box" (not tested! please submit an issue if this does not work!):
 
-You need to recompile the code, which is done by any of the `python do.py build-LANG` or
-`python do.py run-LANG` commands (where `LANG` is one of the supported languages).
 
-Experiments will now use the new dimensions.
+##### 3. Recompile the code
 
-##### 4. Post-processing
+Once you are happy with your changes, you need to regenerate the bindings and recompile them.
+See `DEVELOPMENT.md` in the root of this repository for instructions on how to do that.
+You can also just push to Github if you forked the repository and have the CI job build all bindings for you.
+Once CI has finished, there are artifacts available for download with all the bindings pre-built.
 
-The (probably) only changes that need to be made in the postprocessing are in `cocopp.testbedsettings`. Search for the corresponding `Testbed` class (there is one per test suite, for example `GECCOBBOBTestbed` for the `bbob` test suite). In each `Testbed` class, there are variables that are related to the displayed dimensions. If you change these accordingly, it might run already "out of the box" (not tested! please submit an issue if this does not work!):
+Experiments and post-processing will now use the new dimensions.
 
 ```python
 import cocopp