Remove mentions of new .contract file

README.md

@@ -89,8 +89,8 @@ In order to build the contract just execute these commmands in the `flipper` fol
 cargo contract build
 ```
 
-As a result you'll get a file `target/flipper.wasm` file, a `metadata.json` file and a `<contract-name>.contract` file in the `target` folder of your contract.
-The `.contract` file combines the Wasm and metadata into one file and needs to be used when deploying the contract.
+As a result you'll get a file `target/flipper.wasm` file and a `metadata.json` file in the `target` folder of your contract.
+These need to be used when deploying the contract.
 
 
 ## Hello, World! ‒ The Flipper

examples/README.md

@@ -20,8 +20,7 @@ To build a single example and generate the contracts Wasm file, navigate to the
 
 `cargo contract build`
 
-You should now have an optimized `<contract-name>.wasm` file, a `metadata.json` file and a `<contract-name>.contract` file in the `target` folder of your contract.
-The `.contract` file combines the Wasm and metadata into one file and can be used for deployment.
+You should now have an optimized `<contract-name>.wasm` and a `metadata.json` file in the `target` folder of your contract.
 
 ## License
 

examples/delegator/README.md

@@ -13,11 +13,10 @@ In order to test this bundle of smart contracts you need to do the following:
 
 1. Compile all dependencies of the Delegator smart contract using the `./build-all.sh` script.
    As usual you will receive their respective Wasm blobs in their respective `target` folders.
-   For the delegator (the root of the example) you will additionally get the smart contract as
-   `delegator.contract` in the `target` folder. This file contains the contracts ABI (i.e.
-   metadata) bundled together with its Wasm blob.
-   Note: You won't need a `.contract` file for the other smart contracts `adder`, `subber` and
-         `accumulator`, since we won't operate on them using the Polkadot UI.
+   For the delegator (the root of the example) you will additionally get a `metadata.json`
+   in the `target` folder. This file contains the contracts ABI (i.e. metadata).
+   Note: You won't need a `metadata.json` file for the other smart contracts `adder`, `subber` and
+         `accumulator`, since we won't operate on them using the UI.
 1. Put the Wasm blobs of Accumulator, Adder, Subber and the Delegator on the chain via `put_code` command.
    While doing so note down their respective code hashes that you can inspect by extracting this information
    out from the signalling events upon putting the code on the chain.