Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 1 addition & 8 deletions content/kit/pi/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,13 +18,6 @@ Please do not attempt to modify the software on the Raspberry Pi. It has been co
## Updating your Pi
Keeping your kit up to date is very important. It enables us to deploy new features, as well as fix bugs.

There are 2 ways of updating your kit:

- [Using an `update.tar.xz` file](update-file)
- [Flashing your SD card](sd-card)
We have documentation on [Flashing your SD card](sd-card).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This reads a little oddly, perhaps this?:

You can update your Pi by flashing your SD card.


There is a separate list of [all published updates](/updates).

{{% notice tip %}}
Using the update file is the recommended way to update your kit.
{{% /notice %}}
29 changes: 0 additions & 29 deletions content/kit/pi/update-file.md

This file was deleted.

14 changes: 2 additions & 12 deletions content/updates/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,19 +2,9 @@
title: Updates
---

Keeping your kit up to date is very important. It enables us to deploy new features, as well as fix bugs.

The following table outlines the updates which have been published, each of
which is available in two formats:

* an [update file](/kit/pi/update-file)
* a [full image](/kit/pi/sd-card)

The update files are the easiest way to apply an update and are the recommended
approach. The full images are provided in case an update goes wrong or you need
to completely wipe your Pi for some reason.
Keeping your kit up to date is very important. It enables us to deploy new features, as well as fix bugs. The following table outlines the updates which have been published.

Once you have downloaded the file you need, refer to the documentation on
[updating your pi](/kit/pi/#updating-your-pi) to apply the update.

Each update file is a complete upgrade. Each file contains the changes of those before it. If you need to jump up multiple versions, you can do so by using the latest file.
Each file contains the changes of those before it. If you need to jump up multiple versions, you can do so by using the latest file.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can probably just drop this -- it was thought to be needed as the behaviour of the update files is non-obvious. The behaviour of flashing the Pi is somewhat clearer IMO.

(Not sure if I'm biased by know what the flashing is doing though?)

If we do want to keep this, then maybe explain why the statement is the case? Perhaps something like:

Flashing an image file replaces all the software on the Pi with the versions in the image, so you only need to install the one that you want to use.

Even then, I think that reads oddly as we're omitting a detail about why that comment is needed.

8 changes: 0 additions & 8 deletions layouts/updates/list.html
Original file line number Diff line number Diff line change
Expand Up @@ -7,21 +7,13 @@
<th></th>
<th>Version number</th>
<th>Release Date</th>
<th>Update File Download</th>
<th>Image Download</th>
</tr>
{{ range .Pages.ByDate.Reverse }}
<tr>
<td><a href='{{ .RelPermalink }}' title="See a summary of the changes in this release">{{ .Title }}</a></td>
<td>{{ default "N/A" .Params.version }}</td>
<td>{{ .Date.Format "2006-01-02" }}</td>
<td>
{{ if .Params.update }}
<a href='{{ .Params.update }}'>Download <code>update.tar.xz</code></a>
{{ else }}
No update file available
{{ end }}
</td>
<td>
{{ if .Params.image }}
<a href='{{ .Params.image }}'>Download <code>pi-image.img.xz</code></a>
Expand Down