[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

Author: pre-commit-ci[bot]

docs/howto/providers/google.md

@@ -8,45 +8,44 @@ Google Cloud virtual machine.
 (howto-providers-google-resize-disk)=
 
 ## Increasing your boot disk size
-Google Cloud Compute Engine supports *increasing* (but not *decreasing*) the size of existing disks.
-If you selected a boot disk with a supported version of **Ubuntu** or **Debian** as the operating 
+
+Google Cloud Compute Engine supports _increasing_ (but not _decreasing_) the size of existing disks.
+If you selected a boot disk with a supported version of **Ubuntu** or **Debian** as the operating
 system, then your boot disk can be resized easily from the console with these steps.
 
 :::{note}
-Google Cloud resizes the root partition and file system for *boot* disks with *public* images
-(such as the TLJH supported **Ubuntu** and **Debian** images) automatically after your increase 
-the size of your disk. If you have any other *non-boot* disks attached to your instance, you 
-will need to perform extra steps yourself after resizing your disk. For more information on 
-this and other aspects of resizing persistent disks, see 
-[Google's documentation](https://cloud.google.com/compute/docs/disks/resize-persistent-disk). 
+Google Cloud resizes the root partition and file system for _boot_ disks with _public_ images
+(such as the TLJH supported **Ubuntu** and **Debian** images) automatically after your increase
+the size of your disk. If you have any other _non-boot_ disks attached to your instance, you
+will need to perform extra steps yourself after resizing your disk. For more information on
+this and other aspects of resizing persistent disks, see
+[Google's documentation](https://cloud.google.com/compute/docs/disks/resize-persistent-disk).
 :::
 
-
 1. Go to [Google Cloud Console -> Compute Engine -> VM instances](https://console.cloud.google.com/compute/instances) and select your TLJH instance.
 
-
 1. Scroll down until you find your boot disk and select it.
+
    ```{image} ../../images/providers/google/boot-disk-resize.png
    :alt: Boot disk with Ubuntu jammy image
    ```
 
-
 1. Select **Edit** in the top menu. This may require selecting the kebab menu (the 3 vertical dots).
+
    ```{image} ../../images/providers/google/boot-disk-edit-button.png
    :alt: Disk edit button
    ```
 
-
 1. Update the **Size** property and save the changes at the bottom of the page.
+
    ```{image} ../../images/providers/google/boot-disk-resize-properties.png
    :alt: Boot disk size property
    ```
 
-
 1. Reboot the VM instance by logging into your TLJH, opening the terminal, and running `sudo reboot`.
    You will lose your connection to the instance while it restarts. Once it comes back up, your disk
-   will reflect your changes. You can verify that the automatic resize of your root partition and 
-   file system took place by running `df -h` in the terminal, which will show the size of the disk 
+   will reflect your changes. You can verify that the automatic resize of your root partition and
+   file system took place by running `df -h` in the terminal, which will show the size of the disk
    mounted on `/`:
    ```bash
    $ df -h

docs/troubleshooting/providers/google.md

@@ -5,11 +5,12 @@ TLJH on Google Cloud, and how they have fixed them!
 
 ## Viewing VM instance logs
 
-In addition to [installer, JupyterHub, traefik, and other logs](#troubleshooting-logs) 
+In addition to [installer, JupyterHub, traefik, and other logs](#troubleshooting-logs)
 you can view VM instance logs on Google Cloud to help diagnose issues. These logs will contain
 detailed information and error stack traces and can be viewed from
-[Google Cloud Console -> Compute Engine -> VM instances](https://console.cloud.google.com/compute/instances). 
+[Google Cloud Console -> Compute Engine -> VM instances](https://console.cloud.google.com/compute/instances).
 Once you select your TLJH instance, select **Serial port 1 (console)**:
+
 ```{image} ../../images/providers/google/serial-port-console.png
 :alt: Serial port 1 (console) under Logs heading
 ```
@@ -37,10 +38,10 @@ your server is using.
 If your boot disk becomes full, this can cause your instance to become unavailable,
 among other problems. If your instance appears up and running in the console but
 you cannot access it at your configured external IP/domain name, this could be caused
-by a lack of disk space. 
+by a lack of disk space.
 
-You can explore your [VM logs in the console](#viewing-vm-instance-logs) to determine 
-if any issues you are experiencing indicate disk space issues. 
+You can explore your [VM logs in the console](#viewing-vm-instance-logs) to determine
+if any issues you are experiencing indicate disk space issues.
 
-To resolve these types of issues, you can 
+To resolve these types of issues, you can
 [increase your boot disk size](#howto-providers-google-resize-disk).