Made dev / development container usage consistent in the documentation.

Signed-off-by: davem-bis <68955845+davem-bis@users.noreply.github.com>

Author: davem-bis

docs/development.md

@@ -18,14 +18,14 @@ The development environment of SQLMesh depends both on:
 * Symbolic links in the repository which, whilst available on Windows, typically require additional permissions for the process running git, and;
 * Some Python functionality (e.g. `SIGUSR1`) that is only available on UNIX systems. Whilst this functionality is gated so shouldn't error on Windows, the development container enables its use.
 
-For the Python functionality, a dev container is provided to develop against Ubuntu 24 with Python 3.12.
+For the Python functionality, a development container is provided to develop against Ubuntu 24 with Python 3.12.
 
 For symbolic links, you must ensure that when checking out the repository:
 
-* The git configuration `core.symlinks` is set to `true` (this also needs to be done before bind mount, i.e. when the dev container is started)
+* The git configuration `core.symlinks` is set to `true` (this also needs to be done before bind mount, i.e. when the development container is started)
 * The process that git runs as is permitted to create symbolic links. This can typically be done by running git as an administrator, or enabling [developer mode on Windows](https://learn.microsoft.com/en-us/windows/advanced-settings/developer-mode).
 
-Dev containers are supported by [a number of IDEs](https://containers.dev/supporting.html). For developers using VSCode,  [Microsoft has a tutorial on how to use dev containers](https://code.visualstudio.com/docs/devcontainers/tutorial).
+Development containers are supported by [a number of IDEs](https://containers.dev/supporting.html). For developers using VSCode,  [Microsoft has a tutorial on how to use development containers](https://code.visualstudio.com/docs/devcontainers/tutorial).
 
 ## Virtual environment setup