feat: amend doc from comments

near · Jun 3, 2024 · c509f7f · c509f7f
1 parent f077bdd
commit c509f7f
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -39,6 +39,7 @@ This will scaffold a basic template for you 😎
 - Find [source code examples](./examples) with common use cases
 - Lookup available features in [API reference](https://near.github.io/near-sdk-js/)
 - 🏠 Learn more about NEAR on our [Documentation website](https://docs.near.org/)
+- Breaking features diff from [SDK 2.0.0 to 1.0.0](near-sdk-js@2.0.0-diff-1.0.0.md)
 
 ## Contributing
 

diff --git a/near-sdk-js@2.0.0-diff-1.0.0.md b/near-sdk-js@2.0.0-diff-1.0.0.md
@@ -1,4 +1,4 @@
-# Breaking features from SDK 2.0.0 diff from 1.0.0
+# Breaking features diff from SDK 2.0.0 to 1.0.0
 ## borsh data de/serializer for contract state
 * using for: new contracts or migrate from a borsh serialized contract
 [example](https://github.com/near/near-sdk-js/blob/develop/examples/src/status-message-borsh.js)
@@ -161,7 +161,7 @@ export class Contract {
     }
 }
 ```
-In [near-sdk-js 2.0.0](https://www.npmjs.com/package/near-sdk-js/v/2.0.0-0) With schemas, this is no longer needed, as the SDK can correctly infer how to decode the Nested Collections:
+In [near-sdk-js 2.0.0](https://www.npmjs.com/package/near-sdk-js/v/2.0.0) With schemas, this is no longer needed, as the SDK can correctly infer how to decode the Nested Collections:
 
 ```typescript
 @NearBindgen({})