commit 4ab3ff82
Author: Jason Kridner <jkridner@beagleboard.org>
Date:   Tue Oct 25 21:38:16 2022 -0400

    More spelling fixes

commit fce576ba
Author: Jason Kridner <jkridner@beagleboard.org>
Date:   Tue Oct 25 13:52:28 2022 -0400

    Fixed a bunch of spelling and linking errors

commit 185218ee
Merge: 39c2dd78 c3b7fb7f
Author: Jason Kridner <jkridner@beagleboard.org>
Date:   Mon Oct 24 13:58:46 2022 -0400

    Merge branch 'main' of git.beagleboard.org:docs/docs.beagleboard.io

commit 39c2dd78
Author: Jason Kridner <jkridner@beagleboard.org>
Date:   Mon Oct 24 13:54:54 2022 -0400

    books/pru-cookbook/code: fix some spelling issues

commit c3de7ef6
Author: Jason Kridner <jkridner@beagleboard.org>
Date:   Mon Oct 24 13:44:15 2022 -0400

    books/pru-cookbook: fix references to code

commit c4a51c22
Author: Jason Kridner <jkridner@beagleboard.org>
Date:   Mon Oct 24 12:18:03 2022 -0400

    books/pru-cookbook: move code to submodule

Add AI-64 connectors table & fix text

See merge request docs/docs.beagleboard.io!29

Original from benedict.hewson (https://forum.beagleboard.org/t/bbai-64-pinmux-spreedsheet/32418/6)

commit 11364bf5
Author: Jason Kridner <jkridner@beagleboard.org>
Date:   Fri Sep 30 10:06:24 2022 -0400

    We are releasing 0.0 and starting work on 1.0, yes?

commit 82ad6b70
Merge: 78a5c328 23cbaef2
Author: Jason Kridner <jkridner@beagleboard.org>
Date:   Thu Sep 29 22:27:34 2022 -0400

    Merge branch '0.0' into 'main'

    Fixes for gitlab-build.sh when tag is not on branch

    See merge request jkridner/docs.beagleboard.io!3

commit 23cbaef2
Author: Jason Kridner <jkridner@beagleboard.org>
Date:   Thu Sep 29 22:27:34 2022 -0400

    Fixes for gitlab-build.sh when tag is not on branch

commit 78a5c328
Author: Jason Kridner <jkridner@beagleboard.org>
Date:   Thu Sep 29 15:22:25 2022 -0400

    Versioning proposal

    * I believe our next release should be considered 1.0. Only major
      releases should make incompatible URLs and I believe we should...

Fixes for gitlab-build.sh when tag is not on branch

See merge request jkridner/docs.beagleboard.io!3

* I believe our next release should be considered 1.0. Only major
  releases should make incompatible URLs and I believe we should be free
  to do that for our next "release". This means we can be free to make a
  0.1 stable release if we want that remains URL compatible. I don't
  know why right now. I just feel we should be working towards 1.0,
  not 0.1 when we already have a release. Please feel free to reject.
* For non-tagged updates, I'm thinking the extra-version should be
  something like "wip" to show that it isn't published to the main
  documents site yet.
* I think we should pull the major/minor/extra from the tag, instead of
  branch, and expect it to be used appropriately.
* I know it isn't the prettiest thing, but having a date for the
  patchlevel is super easy to automate and super easy to understand. I
  trust Robert's experience on this.
* I don't know the real purpose of VERSION_TWEAK, but it will be updated
  in case of more than one commit in a day.

What is the process for this? Currently, it seems very error prone.

Add BB-Config projects documents

See merge request !26