Apply suggestions from code review

src/configuration.rst

@@ -22,7 +22,7 @@ aw-server-rust
 
 - :code:`host` Hostname to start the server on. Currently only :code:`localhost` or :code:`127.0.0.1` are supported.
 - :code:`port` Port number to start the server on.
-- :code:`cors` Enable CORS (Cross-Origin Resource Sharing) for the server. This is useful if you want to access the server from a different domain than the one it's hosted on.
+- :code:`cors` List of allowed origins for CORS (Cross-Origin Resource Sharing). Useful in testing and development to let other origins access the ActivityWatch API, such as aw-webui in development mode on port 27180.
 
 aw-client
 ---------

src/examples/writing-watchers.rst

@@ -1,4 +1,4 @@
-Writing your first watcher in python
+Writing your first watcher in Python
 ====================================
 
 Writing watchers for ActivityWatch is pretty easy, all you need is the :code:`aw-client` library.
@@ -34,11 +34,11 @@ This example will describe how to:
 
 .. literalinclude:: client.py
 
-Writing your first watcher in rust
+Writing your first watcher in Rust
 ==================================
 
-To get started with writing watchers in Rust, you need to add the `aw-client-rust` and `aw-model` crates to your `Cargo.toml` file.
-The most upto date versions depend directly on :gh-aw:`aw-server-rust`.
+To get started with writing watchers in Rust, you need to add the ``aw-client-rust`` and ``aw-model`` crates to your ``Cargo.toml`` file.
+The most up-to-date versions depend directly on :gh-aw:`aw-server-rust`.
 
 .. literalinclude:: Cargo.toml