contract: minor fix s/PowReward/PoWReward/ to be consistent in logs

src/contract/money/src/client/pow_reward_v1.rs

@@ -80,7 +80,7 @@ pub struct PoWRewardCallBuilder {
 
 impl PoWRewardCallBuilder {
     fn _build(&self, value: u64) -> Result<PoWRewardCallDebris> {
-        debug!(target: "contract::money::client::pow_reward", "Building Money::PowRewardV1 contract call");
+        debug!(target: "contract::money::client::pow_reward", "Building Money::PoWRewardV1 contract call");
 
         // In this call, we will build one clear input and one anonymous output.
         // Only DARK_TOKEN_ID can be minted as PoW reward.

src/contract/money/src/entrypoint/pow_reward_v1.rs

@@ -172,11 +172,11 @@ pub(crate) fn money_pow_reward_process_update_v1(
     let fees_db = wasm::db::db_lookup(cid, MONEY_CONTRACT_FEES_TREE)?;
 
     // Generate the accumulator for the next height
-    msg!("[PowRewardV1] Creating next height fees accumulator");
+    msg!("[PoWRewardV1] Creating next height fees accumulator");
     wasm::db::db_set(fees_db, &serialize(&(update.height + 1)), &serialize(&0_u64))?;
 
     // This will just make a snapshot to match the coins one
-    msg!("[PowRewardV1] Updating nullifiers snapshot");
+    msg!("[PoWRewardV1] Updating nullifiers snapshot");
     wasm::merkle::sparse_merkle_insert_batch(
         info_db,
         nullifiers_db,