projects objectives (#128)

* kafka cron

* raft with open telemetry

* Update projects/raft-otel/README.md

Co-authored-by: Daniel Wagner-Hall <dawagner@gmail.com>

---------

Co-authored-by: Daniel Wagner-Hall <dawagner@gmail.com>

projects/kafka-cron/README.md

@@ -10,9 +10,10 @@ In this project we're going to build a simple distributed `cron` system, based o
 
 ## Learning Objectives
 
-- How can we use a distributed queue in software architecture?
-- How can we deal with errors in a system based on distributed queues?
-- How can we instrument a complex application with metrics? How should we design alerting?
+- Use a distributed queue in software architecture
+- Deal with errors in a system based on distributed queues
+- Instrument a complex application with metrics
+- Design alerting in a complex application
 
 Timebox: 5 days
 

projects/raft-otel/README.md

@@ -9,11 +9,13 @@ forhugo-->
 In this project we're going to build (or reuse) an implementation of RAFT, a distributed consensus algorithm, and
 we are going to use distributed tracing to understand its behaviour.
 
-Learning Objectives
+## Learning Objectives
 
-- How is distributed tracing different from logging and from metrics?
-- How can we use distributed tracing to get a detailed understanding of complex application behaviour?
-- How can costs of distributed tracing be minimized?
+- Describe the differences between distributed tracing and logging and metrics
+- Implement RAFT
+- Instrument an application with distributed tracing
+- Use distributed tracing to get a detailed understanding of complex application behaviour
+- Minimise costs of distributed tracing
 
 Timebox: 5 days