Image cleanup

- Moving some images from the create wallet page back to the first use page, since they belong into that flow and are used in that page.
- Adding some missing image extensions.
- Fixing some image sizes.

pages/first-use.md

@@ -28,7 +28,7 @@ Ideally, users already clearly understand the application benefits and unique fe
 	big = "/assets/images/first-use/info-big.png"
 	alt-text = "Info screens to explain the app purpose and essential features"
 	width = 800
-	height = 417
+	height = 418
 %}
 
 Since the application requires a lot of storage, we may want to offer users some simple options, particularly on smart phones. Ideally, the application detects available drives and space, and makes an appropriate recommendation that the user only needs to confirm.
@@ -41,7 +41,7 @@ First, the user chooses between pruning and storing all downloaded blocks. They
 	big = "/assets/images/first-use/storage-amount-big.png"
 	alt-text = "Screens for choosing between pruned or full block data storage"
 	width = 800
-	height = 417
+	height = 418
 %}
 
 Then the user decides where to keep downloaded data. They can easily choose desired storage location if the default one is not preferred or has not enough space available. 
@@ -52,31 +52,31 @@ Then the user decides where to keep downloaded data. They can easily choose desi
 	big = "/assets/images/first-use/storage-location-big.png"
 	alt-text = "Screen for choosing default or custom storage location"
 	width = 800
-	height = 417
+	height = 418
 %}
 
 After that, user can continue to [create wallet]({{ '/milestones/1-4-create' | relative_url }}), where at the end of the process they begin initial block download. It's a time-consuming activity that users are typically not familiar with from other applications. The following screen ensures that they understand what will happen next, when they will navigate the application independently.
 
 Bandwidth may also be limited or expensive for the user, particularly on mobile. The initial block download is particularly problematic, so we may want to ensure that users are guided towards the best option. Also see [connection settings]({{ '/settings/connection/' | relative_url }}).
 
 {% include picture.html
-	image = "/assets/images/create-wallet/ibd-and-connection.png"
-	retina = "/assets/images/create-wallet/ibd-[email protected]"
-	big = "/assets/images/create-wallet/ibd-and-connection-big.png"
+	image = "/assets/images/first-use/ibd-and-connection.png"
+	retina = "/assets/images/first-use/ibd-[email protected]"
+	big = "/assets/images/first-use/ibd-and-connection-big.png"
 	alt-text = "Screen that prepares the user for the initial block download, as well as connection settings"
 	width = 800
-	height = 417
+	height = 418
 %}
 
 On Android, a persistent system notification is required to prevent the operating system from pausing the node. This screen explains that to users and prepares them for making an informed decision about accepting or rejecting notification permissions. "Enable" then presents the user with the OS permission request. This can be changed later in OS settings (not in application settings).
 
 {% include picture.html
-	image = "/assets/images/create-wallet/notifications.png"
-	retina = "/assets/images/create-wallet/[email protected]"
-	big = "/assets/images/create-wallet/notifications-big.png"
+	image = "/assets/images/first-use/notifications.png"
+	retina = "/assets/images/first-use/[email protected]"
+	big = "/assets/images/first-use/notifications-big.png"
 	alt-text = "Screen explaining the rationale and use of notifications"
 	width = 800
-	height = 551
+	height = 418
 %}
 
 After these steps, users are navigated to the [block clock]({{ '/block-clock/' | relative_url }}), which in case of first use then connects to the network and starts the initial block download.

pages/milestones/1-4-create.md

@@ -43,51 +43,51 @@ During the onboarding flow, the user is informed that only single-sig wallets ar
 	big = "/assets/images/create-wallet/onboarding-wallet-features-big.png"
 	alt-text = "An informational screen describing supported wallet features"
 	width = 800
-	height = 711
+	height = 417
 %}
 
 Creating single-sig wallet starts with a screen that introduces user to the concept of wallet stored on user's hard drive with option to protect it with a password.
 
 {% include picture.html
 	image = "/assets/images/create-wallet/wallet-info.png"
 	retina = "/assets/images/create-wallet/wallet-[email protected]"
-	big = "/assets/images/create-wallet/wallet-info.png"
+	big = "/assets/images/create-wallet/wallet-info-big.png"
 	alt-text = "An informational screen describing introducing single-sig wallet"
 	width = 800
-	height = 711
+	height = 417
 %}
 
 Next step is to come up with wallet name, that will also be used as the name of the .dat file stored on user's hard drive.
 
 {% include picture.html
 	image = "/assets/images/create-wallet/name.png"
 	retina = "/assets/images/create-wallet/[email protected]"
-	big = "/assets/images/create-wallet/name.png"
+	big = "/assets/images/create-wallet/name-big.png"
 	alt-text = "Screen prompting user to input wallet name"
 	width = 800
-	height = 711
+	height = 418
 %}
 
 Now it's time to decide, If the wallet should be encrypted by a password. This step is critical, because in case of loosing the password, restoring the wallet is virtually impossible. That's why this step is forcing users to slow down a bit and confirm they understand the significance of this by using a toggle, which enables them to continue the flow. Users can also skip this step to create a wallet without encryption.
 
 {% include picture.html
 	image = "/assets/images/create-wallet/password.png"
-	retina = "/assets/images/create-wallet/password.png"
-	big = "/assets/images/create-wallet/password.png"
+	retina = "/assets/images/create-wallet/password@2x.png"
+	big = "/assets/images/create-wallet/password-big.png"
 	alt-text = "Screen that allows to encrypt the wallet with a password"
 	width = 800
-	height = 711
+	height = 417
 %}
 
 Moving forward, private keys are generated in the software and the wallet has been created. Immediately after that, the user is encouraged to create a backup copy of the wallet .dat file. 
 
 {% include picture.html
 	image = "/assets/images/create-wallet/wallet-created.png"
-	retina = "/assets/images/create-wallet/wallet-created.png"
-	big = "/assets/images/create-wallet/wallet-created.png"
+	retina = "/assets/images/create-wallet/wallet-created@2x.png"
+	big = "/assets/images/create-wallet/wallet-created-big.png"
 	alt-text = "Screens showing wallet creation confirmation and encouragement to back up wallet file"
 	width = 800
-	height = 711
+	height = 417
 %}
 
 After these steps, users are navigated to the [block clock]({{ '/block-clock/' | relative_url }}). If IBD already has occurred, users can immediately start using their new empty wallet.