Remove obsolete docs (#527)

The lxd profile does not use the autostart config anymore. Also fix typo

docs/src/charm/reference/architecture.md

@@ -1,5 +1,5 @@
-# K8s charm arcitecture
+# K8s charm architecture
 
 ```{include} /snap/reference/architecture.md
    :start-after: '## Canonical K8s charms'
-```
+```

docs/src/snap/howto/install/lxd.md

@@ -32,7 +32,8 @@ wget https://raw.githubusercontent.com/canonical/k8s-snap/main/tests/integration
 ```
 <!-- markdownlint-restore -->
 
-```{note} For an explanation of the settings in this file, [see below](explain-rules)
+```{note} For an explanation of the settings in this file, [see below]
+(explain-rules)
 ```
 
 To pipe the content of the file into the k8s LXD profile, run:
@@ -70,7 +71,7 @@ lxc exec k8s -- sudo snap install k8s --classic --channel=latest/edge
 ```{note}
 Substitute your desired channel in the above command. Find the
 available channels with `snap info k8s` and see the [channels][]
-explanation page for more details on channels, tracks and versions.  
+explanation page for more details on channels, tracks and versions.
 ```
 
 ## Access Canonical Kubernetes services within LXD
@@ -117,7 +118,8 @@ lxc exec k8s -- sudo k8s bootstrap
 Now, let’s deploy Microbot (please note this image only works on `x86_64`).
 
 ```
-lxc exec k8s -- sudo k8s kubectl create deployment microbot --image=dontrebootme/microbot:v1
+lxc exec k8s -- sudo k8s kubectl create deployment \
+  microbot --image=dontrebootme/microbot:v1
 ```
 
 Then check that the deployment has come up.
@@ -195,9 +197,6 @@ lxc delete k8s
 
 ## Explanation of custom LXD rules
 
-**boot.autostart: “true”**: Always start the container when LXD starts. This is
-needed to start the container when the host boots.
-
 **linux.kernel_modules**: Comma separated list of kernel modules to load before
 starting the container