Fix typos.

Author: jum

LOGGING.md

@@ -1,7 +1,7 @@
 # Logging using log aggregation
 
 There are two ways that I am playing with to perform logging to an
-external logging service: Google Cloud stackdriver lgging and Grafana
+external logging service: Google Cloud stackdriver logging and Grafana
 Cloud Loki. I do like to check all my logs at a central location for all
 my various linux servers. Logging at one central location also has the
 advantage that I can centrally manage any alerting based on strings in
@@ -112,7 +112,7 @@ pipeline:
 ```
 
 The biggest part in the above config is mapping journald priorities to
-stackdriver severities. Please not the use of the Google Cloud
+stackdriver severities. Please note the use of the Google Cloud
 credentials file and the addition of standard instance_id and zone
 resource labels. The directory /var/lib/fluent-bit for journald
 synchronization needs to be created once.

README.md

@@ -205,7 +205,7 @@ due to the fact that docker virtual mounts will not notice if the
 underlying file is recreated upon restarting the listening daemon. For
 the docker socket this does not matter, because if docker is restarted
 all containers will be restarted as well. As a further complication,
-the tailscaled.service files not specify the option to preserve the
+the tailscaled.service files do not specify the option to preserve the
 directory /var/run/tailscale at daemon restart, making a mount of
 /var/run/tailscale instead of the socket not work. But there is an
 option in systemd to make that work, create a directory named