Replace 'LambdaSStore' with 'HookStore' in documentation (#1356)

Signed-off-by: Keith Kowal <keith.kowal@swirldslabs.com>

Author: Reccetech

HIP/hip-1195.md

@@ -34,7 +34,7 @@ transfer. Creating an account hook is analogous to adding a function to a smart
 with the account's privileges when calling Hedera system contracts, just as a smart contract's functions do.
 
 Unlike smart contracts, which must encapsulate trust guarantees for multiple parties, lambda hooks belong to a single
-owner who can directly update their storage via a new `LambdaSStore` transaction that acts on EVM storage slots. This
+owner who can directly update their storage via a new `HookStore` transaction that acts on EVM storage slots. This
 permits fast, heap adjustments to a lambda's behavior with less overhead than a typical `ConsensusSubmitMessage`; and
 far less overhead than a `ContractCall`.
 
@@ -461,15 +461,15 @@ message LambdaStorageSlot {
 }
 ```
 
-After an entity has a lambda, a new `LambdaSStore` transaction supports efficiently updating the lambda's storage. It
+After an entity has a lambda, a new `HookStore` transaction supports efficiently updating the lambda's storage. It
 must be signed by either the entity's controlling key or the admin key set in the lambda's `HookCreationDetails`.
 ```protobuf
 /**
  * Adds or removes key/value pairs in the storage of a lambda.
  * <p>
  * Either the lambda owner's key or the lambda's admin key must sign this transaction.
  */
-message LambdaSStoreTransactionBody {
+message HookStoreTransactionBody {
   /**
    * The id of the lambda whose storage is being updated.
    */
@@ -1066,7 +1066,7 @@ contract OneTimeCodeTransferAllowance is IHieroAccountAllowanceHook {
 ```
 
 As great aficionados of the project, we see one day that `0.0.X` holds our favorite NFT of all, serial `123`; and that a
-`LambdaSStore` from `0.0.X` set the storage slot with key `0x00` to the hash
+`HookStore` from `0.0.X` set the storage slot with key `0x00` to the hash
 `0xc7eba0ccc01e89eb5c2f8e450b820ee9bb6af63e812f7ea12681cfdc454c4687`. We rush to solve the puzzle, and deduce the
 passcode is the string, `"These violent delights have violent ends"`. Now we can transfer the NFT to our account `0.0.U`
 by submitting a `CryptoTransfer` with,
@@ -1088,7 +1088,7 @@ NftTransfer {
 
 Compare this example to the pure smart contract approach, where the project's team would need to write a more complex
 smart contract that is aware of what serial number it currently holds, and makes calls to the HTS system contract to
-distribute NFTs. Instead of the team using `LambdaSStore` to update the passcode with less overhead and cost to
+distribute NFTs. Instead of the team using `HookStore` to update the passcode with less overhead and cost to
 the network than even a `ConsensusSubmitMessage`, they would need to submit a `ContractCall`. Instead of us using a
 `CryptoTransfer` to collect our prize with maximum legibility and minimum cost, we would also need to submit a
 `ContractCall` to the project's smart contract with a significantly higher gas limit.