Merge pull request #1186 from kadena-community/chore/docs/election-tu…

…torial-fixes

chore(docs): fix errors in election dapp tutorial

.changeset/tall-dancers-pay.md

@@ -0,0 +1,5 @@
+---
+'@kadena/docs': patch
+---
+
+fix small errors in election dapp tutorial

packages/apps/docs/src/pages/build/guides/election-dapp-tutorial/04-namespaces.md

@@ -14,8 +14,8 @@ After you have completed this entire tutorial, you may want to deploy your elect
 smart contract to Testnet. Many others like you would perhaps like to do the same.
 If everyone would deploy Pact modules with the same name to the same network, however,
 it would become impossible to distinguish your Pact module from all the others. Therefore,
-it is not allowed to
-deploy a Pact module with a name that already exists on the chain you are deploying to
+it is not allowed to deploy a Pact module with a name that is already used by someone
+else on the chain you are deploying to
 and your deployment transaction will fail with an error if you try. Fortunately,
 Kadena offers a solution to this problem by introducing namespaces. You can create
 your own unique namespace on the blockchain and you get to decide who can update the

packages/apps/docs/src/pages/build/guides/election-dapp-tutorial/05-keysets.md

@@ -189,7 +189,7 @@ file and run it.
 
 ```pact
 (env-data
-  { 'admin-key :
+  { 'admin-keyset :
     { 'keys : [ 'other-public-key ]
     , 'pred : 'keys-all
     }
@@ -268,6 +268,10 @@ the statement `(namespace ns-name)`. Finally, you need to add a signature for th
 to succeed.
 
 ```pact
+(begin-tx)
+  (load "root/ns.pact")
+(commit-tx)
+
 (env-sigs
   [{ 'key  : "368820f80c324bbc7c2b0610688a7da43e39f91d118732671cd9c7500ff43cca"
    , 'caps : []