Updated comments to prevent "unmappable character (0xXX) for encoding…

… UTF-8" errors. (#301) * fix - Signed-off-by: Neeharika-Sompalli <neeharika.sompalli@swirldslabs.com> * Updated comments to prevent "unmappable character (0xXX) for encoding UTF-8" errors. --------- Signed-off-by: Neeharika-Sompalli <neeharika.sompalli@swirldslabs.com>
hashgraph · Aug 15, 2023 · 9e65bc7 · 9e65bc7
1 parent c1de1a1
commit 9e65bc7
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/services/basic_types.proto b/services/basic_types.proto
@@ -1236,7 +1236,7 @@ message TransactionFeeSchedule {
 }
 
 /**
- * The total fee charged for a transaction. It is composed of three components – a node fee that
+ * The total fee charged for a transaction. It is composed of three components - a node fee that
  * compensates the specific node that submitted the transaction, a network fee that compensates the
  * network for assigning the transaction a consensus timestamp, and a service fee that compensates
  * the network for the ongoing maintenance of the consequences of the transaction.

diff --git a/services/contract_call.proto b/services/contract_call.proto
@@ -30,14 +30,14 @@ import "basic_types.proto";
 
 /**
  * Call a function of the given smart contract instance, giving it functionParameters as its inputs.
- * The call can use at maximum the given amount of gas – the paying account will not be charged for
+ * The call can use at maximum the given amount of gas - the paying account will not be charged for
  * any unspent gas.
  *
  * If this function results in data being stored, an amount of gas is calculated that reflects this
  * storage burden.
  *
  * The amount of gas used, as well as other attributes of the transaction, e.g. size, number of
- * signatures to be verified, determine the fee for the transaction – which is charged to the paying
+ * signatures to be verified, determine the fee for the transaction - which is charged to the paying
  * account.
  */
 message ContractCallTransactionBody {

diff --git a/services/schedule_create.proto b/services/schedule_create.proto
@@ -123,7 +123,7 @@ message ScheduleCreateTransactionBody {
    * Setting this to false does not necessarily mean that the transaction will never execute at expiration_time.
    *  For Example - If the signature requirements for a Scheduled Transaction change via external means (e.g. CryptoUpdate)
    *  such that the Scheduled Transaction would be allowed to execute, it will do so autonomously at expiration_time, unless a
-   *  ScheduleSign comes in to “poke” it and force it to go through immediately.
+   *  ScheduleSign comes in to "poke" it and force it to go through immediately.
    *
    * Note: This field is unused and forced to be unset until Long Term Scheduled Transactions are enabled. Before Long Term
    *       Scheduled Transactions are enabled, Scheduled Transactions will _never_ execute at expiration  - they will _only_