Merge branch 'main' of github.com:hubblo-org/scaphandre into main

docs_src/references/exporter-prometheus.md

@@ -50,7 +50,7 @@ And some more deep metrics that you may want if you need to make more complex ca
 - `scaph_host_energy_timestamp_seconds`: Timestamp in seconds when hose_energy_microjoules has been computed. (COUNTER)
 - `scaph_socket_power_microwatts{socket_id="$SOCKET_ID"}`: Power measurement relative to a CPU socket, in microwatts. SOCKET_ID being the socket numerical id (GAUGE)
 
-If you hack scaph or just want to tinvestigate its behavior, you may be interested in some internal metrics:
+If you hack scaph or just want to investigate its behavior, you may be interested in some internal metrics:
 
 - `scaph_self_mem_total_program_size`: Total program size, measured in pages
 
@@ -78,4 +78,4 @@ Here are available labels for the `scaph_process_power_consumption_microwatts` m
 - `exe`: is the name of the executable that is the origin of that process. This is good to be used when your application is running one or only a few processes.
 - `cmdline`: this contains the whole command line with the executable path and its parameters (concatenated). You can filter on this label by using prometheus `=~` operator to match a regular expression pattern. This is very practical in many situations.
 - `instance`: this is a prometheus generated label to enable you to filter the metrics by the originating host. This is very useful when you monitor distributed services, so that you can not only sum the metrics for the same service on the different hosts but also see what instance of that service is consuming the most, or notice differences beteween hosts that may not have the same hardware, and so on...
-- `pid`: is the process id, which is useful if you want to track a specific process and have your eyes on what's happening on the host, but not so practical to use in a more general use case
+- `pid`: is the process id, which is useful if you want to track a specific process and have your eyes on what's happening on the host, but not so practical to use in a more general use case