Update yocto slides to wrynose

slides/yocto-advanced/yocto-advanced.typ

@@ -241,9 +241,9 @@ $ bitbake-getvar DEPLOY_DIR
 NOTE: Starting bitbake server...
 #
 # $DEPLOY_DIR [2 operations]
-#   set? /home/user/yocto-labs/poky/meta/conf/bitbake.conf:440
+#   set? /home/user/yocto-labs/openembedded-core/meta/conf/bitbake.conf:440
 #     "${TMPDIR}/deploy"
-#   set /home/user/yocto-labs/poky/meta/conf/documentation.conf:137
+#   set /home/user/yocto-labs/openembedded-core/meta/conf/documentation.conf:137
 #     [doc] "Points to the general area that the OpenEmbedded build system uses to place images, [...]"
 # pre-expansion value:
 #   "${TMPDIR}/deploy"
@@ -318,7 +318,7 @@ $
 #v(0.5em)
 
 ```sh
-OVERRIDES="arm:armv7a:ti-soc:ti33x:beaglebone:poky"
+OVERRIDES = "arm:armv7a:ti-soc:ti33x:beaglebone:poky"
 
 KERNEL_DEVICETREE:beaglebone = "am335x-bone.dtb" # This is applied
 KERNEL_DEVICETREE:dra7xx-evm = "dra7-evm.dtb"    # This is ignored

slides/yocto-basics/yocto-basics.typ

@@ -13,7 +13,7 @@
 
 === Environment setup
 
-- All Poky files are left unchanged when building a custom image.
+- All Yocto source files are left unchanged when building a custom image.
 
 - Specific configuration files and build repositories are stored in a
   separate build directory.
@@ -28,7 +28,7 @@
 
 - Adds environment variables, used by the build engine.
 
-- Allows you to use commands provided in Poky.
+- Allows you to use commands provided in openembedded-core.
 
 - `source ./oe-init-build-env [builddir]`
 
@@ -88,6 +88,10 @@
       limits.
     ]
 
+  / toolcfg.conf: #block[
+      Used by tools to store build configuration, it should not be modified manually.
+    ]
+
 === Configuring the build
 
 The `conf/local.conf` configuration file holds local user configuration variables: