4 files changed, 1 insertions, 35 deletions
diff --git a/docs/getting-started/docker-container-setup.md b/docs/getting-started/docker-container-setup.md
index d984e5f..48df10a 100644
--- a/docs/getting-started/docker-container-setup.md
+++ b/docs/getting-started/docker-container-setup.md
@@ -192,8 +192,6 @@ based on the AGL Worker image:
 **NOTE:**
 The password for the ID "devel" inside the docker image is "devel".
 
-**WRITER NOTE:** I need to do this and see what this output really looks like.
-
 ```bash
 $ git clone https://git.automotivelinux.org/AGL/docker-worker-generator
 $ cd docker-worker-generator
diff --git a/docs/getting-started/machines/intel.md b/docs/getting-started/machines/intel.md
index bd55fdc..3658408 100644
--- a/docs/getting-started/machines/intel.md
+++ b/docs/getting-started/machines/intel.md
@@ -88,8 +88,6 @@ The build process puts the resulting image in the Build Directory:
 <build_directory>/tmp/deploy/images/intel-corei7-64/
 ```
 
-**WRITER NOTE:** I am not sure what to do with the following information:
-
 An alternative method for building an image is to use the AGL SDK delivered in a Docker container.
 
 There is currently no SDK dedicated to IA but the SDK provided for the Porter Board can build an IA image without changes (just `aglsetup.sh` needs to call for Intel).
diff --git a/docs/getting-started/machines/renesas.md b/docs/getting-started/machines/renesas.md
index fc1d57e..895fe19 100644
--- a/docs/getting-started/machines/renesas.md
+++ b/docs/getting-started/machines/renesas.md
@@ -20,10 +20,6 @@ Renesas development kits.
 
 You can find more information on building images from these resources:
 
-**WRITER NOTE:**
-This following list looks a bit dated.
-Do we want to update these PDFs or are they still useful?
-
 * [AGL-Devkit-Build-your-1st-AGL-Application.pdf](https://iot.bzh/download/public/2016/sdk/AGL-Devkit-Build-your-1st-AGL-Application.pdf)
  Generic guide on how to build various application types (HTML5, native, Qt, QML, …) for AGL.
  This is really about building an application and not the AGL image.
diff --git a/docs/getting-started/troubleshooting.md b/docs/getting-started/troubleshooting.md
index ea3aba1..90c1fae 100644
--- a/docs/getting-started/troubleshooting.md
+++ b/docs/getting-started/troubleshooting.md
@@ -1,12 +1,6 @@
 # Troubleshooting
 
-**WRITER'S NOTE:** This content needs a new home.
-  Most likely it will be in some "how-to" area as most of the information
-  fits that category.
-  For now, I am leaving it here.
-  The other two board-specific troubleshooting sections have been merged
-  into their respective build topics in the section describing how to
-  build an AGL image.
+This topic describes various areas that could cause you problems. 
 
 ## Including Extended Attributes
 
@@ -58,26 +52,6 @@ However, if you do, you must take these steps to copy `xattrs` to the media:
               --xattrs-include='*' --directory=DESTINATION_DIRECTORY --file=agl-demo-platform.....tar.xz
    ```
 
-<!--
-## meta-rust
-
-**WRITER NOTE:** This bug no longer applies.  The people that maintain meta-rust have fixed it.
-See https://github.com/meta-rust/meta-rust/commit/39fd00119cf9267bc6b381d0b7abeebda31faf4e and
-https://github.com/meta-rust/meta-rust/pull/93.
-
-Due to a known bug in the upstream of meta-rust the Yocto/OE recipe for rust-cross may fail while building RVI SOTA Client or another application written in the Rust programming language.
-Until the complete resolution of the issue the workaround is to disable all use of the CXX11 ABI by applying the following lines to **conf/local.conf**:
-
-```bash
-LD_CXXFLAGS_append = " -D_GLIBCXX_USE_CXX11_ABI=0"
-TARGET_CXXFLAGS_append = " -D_GLIBCXX_USE_CXX11_ABI=0"
-CXXFLAGS_append = " -D_GLIBCXX_USE_CXX11_ABI=0"
-
-BUILD_CXXFLAGS_remove_pn-gcc-runtime = "-D_GLIBCXX_USE_CXX11_ABI=0"
-TARGET_CXXFLAGS_remove_pn-gcc-runtime = "-D_GLIBCXX_USE_CXX11_ABI=0" CXXFLAGS_remove_pn-gcc-runtime = "-D_GLIBCXX_USE_CXX11_ABI=0"
-```
--->
-
 ## Screen orientation for Splash and in Weston
 
 Depending of your scren mounting the default orientation of the UI an/or splash screen might be incorrect.