Minor formatting IViewModule and ICoreMetadataViewModule (#384)

storyprotocol · Feb 10, 2025 · 1ffda0a · 1ffda0a
1 parent b0336c2
commit 1ffda0a
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/contracts/interfaces/modules/base/IViewModule.sol b/contracts/interfaces/modules/base/IViewModule.sol
@@ -5,7 +5,7 @@ import { IModule } from "./IModule.sol";
 
 /// @notice View Module Interface
 /// View modules typically are read-only modules that are responsible for displaying
-/// IP-related data in various ways to meet different needs.For instance,
+/// IP-related data in various ways to meet different needs. For instance,
 /// they can display simple/base/core metadata, book specific metadata, license details metadata,
 /// or even IP graph data for the same IPAccount using different View Modules.
 /// This module offers flexibility in selecting which data to display and how to present it.

diff --git a/contracts/interfaces/modules/metadata/ICoreMetadataViewModule.sol b/contracts/interfaces/modules/metadata/ICoreMetadataViewModule.sol
@@ -55,7 +55,7 @@ interface ICoreMetadataViewModule is IViewModule {
     function getCoreMetadata(address ipId) external view returns (CoreMetadata memory);
 
     /// @notice Generates a JSON string formatted according to the standard NFT metadata schema for the IPAsset,
-    ////        including all relevant metadata fields.
+    ///        including all relevant metadata fields.
     /// @dev This function consolidates metadata from both IPAssetRegistry
     ///      and CoreMetadataModule, with "name" from CoreMetadataModule taking precedence.
     /// @param ipId The address of the IPAsset.