Fix typos in documentation comments (#5969)

* Update geyser_plugin_service.rs

* Update zk_token_proof_instruction.rs

geyser-plugin-manager/src/geyser_plugin_service.rs

@@ -45,7 +45,7 @@ impl GeyserPluginService {
     /// Creates and returns the GeyserPluginService.
     /// # Arguments
     /// * `confirmed_bank_receiver` - The receiver for confirmed bank notification
-    /// * `geyser_plugin_always_enabled` -- Subscribe on all types of notifiactions, even if
+    /// * `geyser_plugin_always_enabled` -- Subscribe on all types of notifications, even if
     ///   no config files are passed
     /// * `geyser_plugin_config_file` - The config file path for the plugin. The
     ///   config file controls the plugin responsible

zk-token-sdk/src/zk_token_proof_instruction.rs

@@ -12,7 +12,7 @@
 //! In step 1, the zero-knowledge proof can be included directly as the instruction data or
 //! pre-written to an account. The program determines whether the proof is provided as instruction
 //! data or pre-written to an account by inspecting the length of the data. If the instruction data
-//! is exactly 5 bytes (instruction disciminator + unsigned 32-bit integer), then the program
+//! is exactly 5 bytes (instruction discriminator + unsigned 32-bit integer), then the program
 //! assumes that the first account provided with the instruction contains the zero-knowledge proof
 //! and verifies the account data at the offset specified in the instruction data. Otherwise, the
 //! program assumes that the zero-knowledge proof is provided as part of the instruction data.