rename demo services

Author: puckpuck

content/en/docs/demo/requirements/architecture.md

@@ -60,11 +60,10 @@ Feature flags can be set through the flagd configurator user interface.
 
 ## Orchestration and Deployment
 
-All services run on Kubernetes. The OpenTelemetry Collector should be
-deployed via the OpenTelemetry Operator, and run in a sidecar + gateway mode.
-Telemetry from each pod should be routed from agents to a gateway, and the
-gateway should export telemetry by default to an open source trace + metrics
-visualizer.
+All services run on Kubernetes. The OpenTelemetry Collector should be deployed
+via the OpenTelemetry Operator, and run in a sidecar + gateway mode. Telemetry
+from each pod should be routed from agents to a gateway, and the gateway should
+export telemetry by default to an open source trace + metrics visualizer.
 
 For local/non-Kubernetes deployment, the Collector should be deployed via
 compose file and monitor not only traces/metrics from applications, but also the

content/en/docs/demo/scenarios/recommendation-cache/index.md

@@ -70,11 +70,11 @@ work, and viewing the details allows us to get a better idea of what's going on.
 We can see in our waterfall view that the `app.cache_hit` attribute is set to
 false, and that the `app.products.count` value is extremely high.
 
-Returning to the search UI, select `recommendation` in the Service dropdown,
-and search for `app.cache_hit=true` in the Tags box. Notice that requests tend
-to be faster when the cache is hit. Now search for `app.cache_hit=false` and
-compare the latency. You should notice some changes in the visualization at the
-top of the trace list.
+Returning to the search UI, select `recommendation` in the Service dropdown, and
+search for `app.cache_hit=true` in the Tags box. Notice that requests tend to be
+faster when the cache is hit. Now search for `app.cache_hit=false` and compare
+the latency. You should notice some changes in the visualization at the top of
+the trace list.
 
 Now, since this is a contrived scenario, we know where to find the underlying
 bug in our code. However, in a real-world scenario, we may need to perform