Apply suggestions from code review

Co-authored-by: Techassi <git@techassi.dev>

Author: maltesander

docs/modules/hbase/pages/usage-guide/monitoring.adoc

@@ -16,7 +16,7 @@ and the clients scraping the metrics endpoint need to authenticate against it. T
 between Kubernetes Pods with the xref:home:secret-operator:index.adoc[Secret Operator].
 
 When using Prometheus `ServiceMonitor` for scraping, the `address` label needs relabeling to use the `headless` Service instead of the
-`metrics` Service. This is because per default Prometheus targets the Pod IPs as endpoints, but since the Pod IPs are not
+`metrics` Service. This is because by default Prometheus targets the Pod IPs as endpoints, but since the Pod IPs are not
 part of the certificate, the authentication will fail. Instead, the FQDN of the Pods, which can be added to the certificate, is used, but
 this FQDN is only available through the `headless` Service.
 

rust/operator-binary/src/crd/mod.rs

@@ -719,7 +719,8 @@ impl HbaseRole {
     }
 
     /// Returns required port name and port number tuples depending on the role.
-    /// Hbase versions 2.6.* will have two ports for each role. The metrics are available over the
+    ///
+    /// Hbase versions 2.6.* will have two ports for each role. The metrics are available on the
     /// UI port.
     pub fn ports(&self, hbase: &v1alpha1::HbaseCluster) -> Vec<(String, u16)> {
         vec![