docs: update limitations doc (#14035)

I noticed the "Limitations" section of the docs is out of date; it looks
the same as September '23 when we made the Sandbox release.

Encouragingly, the number of "Limitations" has greatly reduced since
then, so I've deleted lots of sections that aren't true anymore. We've
made progress! I wanted to quickly make these changes, to avoid giving
readers the wrong impression about our progress.

cc @AztecProtocol/devrel - please could someone review?

---------

Co-authored-by: Josh Crites <jc@joshcrites.com>

Author: iAmMichaelConnor

docs/docs/developers/reference/considerations/limitations.md

@@ -28,9 +28,14 @@ Emit encrypted events, or encrypted messages from a private smart contract funct
 
 Execute a private function without the world knowing which function you've executed.
 
+**Private bytecode**
+
+The bytecode of private functions does not need to be distributed to the world; much like real-world contracts.
+
 :::danger
 Privacy is not guaranteed without care.
 Although Aztec provides the tools for private smart contracts, information can still be leaked unless the dapp developer is careful.
+Aztec is still under development, so real-world, meaningful, valuable secrets _should not_ be entrusted to the system.
 This page outlines some best practices to aid dapp developers.
 :::
 

docs/docs/developers/reference/considerations/privacy_considerations.md

@@ -28,9 +28,14 @@ Emit encrypted events, or encrypted messages from a private smart contract funct
 
 Execute a private function without the world knowing which function you've executed.
 
+**Private bytecode**
+
+The bytecode of private functions does not need to be distributed to the world; much like real-world contracts.
+
 :::danger
 Privacy is not guaranteed without care.
 Although Aztec provides the tools for private smart contracts, information can still be leaked unless the dapp developer is careful.
+Aztec is still under development, so real-world, meaningful, valuable secrets _should not_ be entrusted to the system.
 This page outlines some best practices to aid dapp developers.
 :::