remove questions and optional content from manual instrumentaion labs

tutorial/content/labs/instrumentation/manual/logs/index.md

@@ -184,6 +184,7 @@ Since no tracing is set up, the `trace_id` and `span_id` are `0`. There are many
 * https://github.com/open-telemetry/opentelemetry-python
 * https://opentelemetry-python-contrib.readthedocs.io/en/latest/instrumentation/logging/logging.html
 
+<!--
 ### Knowledge check
 
 1. **Question**: OpenTelemetry provides a standardized way to collect and export logs.
@@ -227,3 +228,4 @@ Since no tracing is set up, the `trace_id` and `span_id` are `0`. There are many
 * Learn how to log complex structures
 * Understand the integration of OpenTelemetry logging into Python applications through manual and automatic instrumentation.
 * Review the structure of OpenTelemetry logs and the role of trace and span IDs in log entries.
+-->

tutorial/content/labs/instrumentation/manual/metrics/index.md

@@ -638,6 +638,11 @@ If we pass `DropAggregation`, the SDK will ignore all measurements from the matc
 You have now seen some basic examples of how Views let us match instruments and customize the metrics stream.
 Feel free to add these code snippets to `create_views` and observe the changes in the output.
 
+## finish
+
+Congratulations on successfully completing the lab on metrics!
+
+<!-- 
 ## quiz
 
 {{< quizdown >}}
@@ -667,12 +672,9 @@ Feel free to add these code snippets to `create_views` and observe the changes i
 - [ ] D. Use an `UpAndDownCounter` instrument to track the number of requests
 
 {{< /quizdown >}}
+-->
 
-
-## finish
-
-Congratulations on successfully completing the lab on metrics!
-
+<!-- 
 ### push and pull-based exporter
 
 So far, we have seen how the ConsoleMetricsExporter can be a useful tool when debugging output generated by the SDK.
@@ -739,4 +741,5 @@ The reason is that in Flask's debug mode the code is reloaded after the flask se
 As a result, the Prometheus server tries to bind to a port a second time, which the OS prevents.
 To fix this, set the debug parameter to False.
 Start the app and open [localhost:8000](localhost:8000) in your browser.
-You should now see the metrics being exported in Prometheus text-based exposition format.
+You should now see the metrics being exported in Prometheus text-based exposition format.
+-->

tutorial/content/labs/instrumentation/manual/traces/index.md

@@ -486,6 +486,7 @@ Now, the service should recognize the tracing header of the incoming request and
 Finally, context propagation is working as expected.
 If we were to export spans to a tracing backend, it could analyze the SpanContext of the individual objects and piece together a distributed trace.
 
+<!-- 
 ## quiz
 
 {{< quizdown >}}
@@ -558,6 +559,8 @@ This makes it trivial to share it across different telemetry signals and service
 To implement it simply inherit from the `ResourceDetector` class and override the `detect` method.
 Finally, we simply call the `merge` method on the `Resource` object, which combines both and returns a new object.
 
+-->
+
 ## finish
 
 Congratulations on successfully completing the lab on distributed tracing with OpenTelemetry.