chore: improve contract section

docs/smart-contracts/anatomy/anatomy.md

@@ -12,7 +12,7 @@ import {ExplainCode, Block, File} from '@site/src/components/CodeExplainer/code-
 
 Let's illustrate the basic anatomy of a simple "Hello World" contract. The code on this page comes from our [Hello NEAR repository](https://github.com/near-examples/hello-near-examples) on GitHub.
 
-<ExplainCode languages="js,rust,python,go" >
+<ExplainCode languages="rust,js,python,go" >
 
 <Block highlights='{"js": "1", "rust": "1", "python": "1","go":"3-6"}' fname="hello-near">
 

docs/smart-contracts/anatomy/best-practices.md

@@ -15,6 +15,7 @@ This page provides a collection of best practices for writing smart contracts on
 
 Here we lay out some best practices for writing smart contracts on NEAR, such as:
 
+- [Store Account IDs efficiently](#store-account-ids-efficiently)
 - [Enable overflow checks](#enable-overflow-checks)
 - [Use `require!` early](#use-require-early)
 - [Use `log!`](#use-log)
@@ -25,6 +26,10 @@ Here we lay out some best practices for writing smart contracts on NEAR, such as
 
 ---
 
+## Store Account IDs efficiently
+
+You can save on smart contract storage if using NEAR Account IDs by encoding them using base32. Since they consist of `[a-z.-_]` characters with a maximum length of 64 characters, they can be encoded using 5 bits per character, with terminal `\0`. Going to a size of 65 * 5 = 325 bits from the original (64 + 4) * 8 = 544 bits. This is a 40% reduction in storage costs
+
 ## Enable overflow checks
 
 It's usually helpful to panic on integer overflow. To enable it, add the following into your `Cargo.toml` file: