Fix update package structure in contributing guide
@@ -46,15 +46,15 @@ This is a high level overview of the project structure:
[options="header"]
|=======================
| Path | Content
-| link:/cmd[/cmd] | Contains the entry points (the *main* functions) for the **camel-k** binary and the **kamel** client tool.
-| link:/build[/build] | Contains scripts used during make operations for building the project.
+| link:/cmd[/cmd] | Contains the entry points (the *main* functions) for the **camel-k** binary (manager) and the **kamel** client tool.
+| link:/build[/build] | Contains build data used by the operator-sdk.
| link:/deploy[/deploy] | Contains Kubernetes resource files that are used by the **kamel** client during installation. The `/deploy/resources.go` file is kept in sync with the content of the directory (`make build-embed-resources`), so that resources can be used from within the go code.
| link:/docs[/docs] | Contains the documentation website based on https://antora.org/[Antora].
| link:/pkg[/pkg] | This is where the code resides. The code is divided in multiple subpackages.
| link:/runtime[/runtime] | The Java runtime code that is used inside the integration Docker containers.
+| link:/script[/script] | Contains scripts used during make operations for building the project.
| link:/test[/test] | Include integration tests to ensure that the software interacts correctly with Kubernetes and OpenShift.
-| link:/tmp[/tmp] | Scripts and Docker configuration files used by the operator-sdk.
-| /vendor | Project dependencies (not staged in git).
+| /vendor | Project dependencies (staged in git).
| link:/version[/version] | Contains the global version of the project.
|=======================
