GITBOOK-34: No subject

SUMMARY.md

@@ -12,7 +12,7 @@
 * [Automatic Instrumentation in the IDE](instrumentation/automatic-instrumentation-in-the-ide/README.md)
   * [Spring, Spring Boot, Dropwizard and default](instrumentation/automatic-instrumentation-in-the-ide/spring-spring-boot-dropwizard-and-default.md)
   * [Quarkus, Micronaut](instrumentation/automatic-instrumentation-in-the-ide/quarkus-micronaut.md)
-* [Instrumenting your code from terminal](instrumentation/instrumenting-your-code-from-terminal.md)
+* [Instrumenting your code in CI/Staging or the terminal](instrumentation/instrumenting-your-code-in-ci-staging-or-the-terminal.md)
 
 ## Digma Core Concepts
 

digma-core-concepts/environments.md

@@ -7,4 +7,13 @@ description: >-
 
 # Environments
 
-In order to better compare and aggregate data, it is 
+### Why it's important to have more than one environment
+
+Digma excels in analyzing observability data, detecting changes, and measuring baselines. Lumping together data from dev, test, load testing, and production would create a huge mess with many strange statistical artifacts. Each time you run a load test you'll notice huge performance degradations while running in debug mode would manifest bugs in code that hasn't yet been checked in.
+
+To bring some order into this chaos, Digma uses environments as an abstraction to measure data from different deployment stages and use cases separately.
+
+### How to create environments
+
+Private environments are easy to create in your local deployment.
+

instrumentation/instrumenting-your-code-in-ci-staging-or-the-terminal.md

@@ -0,0 +1,3 @@
+# Instrumenting your code in CI/Staging or the terminal
+
+If you're running