diff --git a/STANDARDS.md b/STANDARDS.md
index 6d7f184..1c33c89 100644
--- a/STANDARDS.md
+++ b/STANDARDS.md
@@ -6,18 +6,18 @@ Examples uses mostly the same coding standards as Drupal core.
 If you see a discrepancy between the coding standards tools used by core and
 those used by Examples, please file an issue so that Examples can follow core.
 
-Examples uses the phpcs tool to allow for checking PHP coding standards. We also
-use eslint for JavaScript coding standards.
+Examples uses the `phpcs` tool to allow for checking PHP coding standards. We
+use the `drupal/coder` project for Drupal-specific coding standards.
 
-Examples has a `phpcs.xml.dist` file at the root of the project. This file
-specifies the current coding standards 'sniffs' which code in the project must
-pass.
+We also use `eslint` for JavaScript coding standards.
 
-The `phpcs.xml.dist` file is used by a tool called PHP_CodeSniffer (`phpcs`).
+Examples has a `phpcs.xml.dist` file at the root of the project. phpcs uses this
+file to specify the current coding standards 'sniffs' which code in the project
+must pass.
 
 Contributors should install `phpcs` in their local Drupal installation, and then
 use that to run `phpcs` against Examples as part of their development and review
-process.
+process. (See details below on how to install and run this tool.)
 
 Contributors can also patch the `phpcs.xml.dist` file itself, in order to fix
 the codebase to pass a given rule or sniff. Patches which do this should be
@@ -47,6 +47,10 @@ Like this:
     $ ../vendor/bin/phpcs -e --standard=Drupal
     // Shows you a bunch of Drupal-related sniffs.
 
+Note that there is an issue to require Coder and phpcs as part of Drupal core:
+https://www.drupal.org/node/2744463 Once this issue is fixed, you shouldn't need
+to install phpcs before using it.
+
 Running phpcs
 -------------
 
diff --git a/TESTING.md b/TESTING.md
index ba753f5..1130ed8 100644
--- a/TESTING.md
+++ b/TESTING.md
@@ -15,6 +15,12 @@ the testbot's behavior.
 You can find information on how to run `run-tests.sh` locally here:
 https://www.drupal.org/node/645286
 
+Examples is always targeted to dev branch of Drupal core for the latest release.
+As of this writing, the latest release of Drupal core is 8.2.5, which means
+development for Examples should be against the Drupal 8.2.x development branch.
+When Drupal 8.3.0 is released, we'll start targeting Examples to 8.3.x, and so
+on.
+
 You should at least run `run-tests.sh` locally against all the changes in your
 patch before uploading it.
 
@@ -27,8 +33,68 @@ suggested workaround for this, since there is no best practice to demonstrate as
 an example. There is, however, this issue in core:
 https://www.drupal.org/node/2499239
 
+How To Run The Tests In The Drupal UI
+-------------------------------------
+
+Generally, you should run tests from the command line. This is generally easier
+than using Drupal's testing UI. However, here's how you can do it that way:
+
+Enable the Testing module.
+
+Visit the test list page at `admin/config/development/testing`.
+
+Since the tests are organized by module, you can search for a module name and
+get all the tests for that module. For instance, type in 'node_type_example' for
+all the tests related to that module.
+
+Click the check boxes next to the tests you want to run. If you find this
+tedious, it's time to learn to use the command line. :-)
+
+Click 'Run Tests.' You're now running the tests.
+
+Step-by-step: How To Run The Tests
+-----------------------------------
+
+Begin with an installed Drupal codebase. Make a codebase, set up the database,
+etc. Note that you can use an existing Drupal instance but the best practice is
+to start fresh. Something not working right? Try a new installation.
+
+Use the dev branch of core for the latest release of Drupal. As of this writing,
+it's 8.2.x. When Drupal 8.3.0 is released, we'll target 8.3.x.
+
+Open the terminal window and move to the root directory of the Drupal
+installation:
+
+	$ cd path/to/drupal
+
+Put Examples into the `modules/` folder of the Drupal installation. If you are
+doing development on Examples, you should have already checked out the git
+repository into `modules/`, like this:
+
+	$ git clone --branch 8.x-1.x https://git.drupal.org/project/examples.git modules/examples
+
+Now you can run `run-tests.sh`, which, despite having a `.sh` suffix is not a
+shell script. It's a PHP script.
+
+You'll use the `--directory` option to have the test runner scan the Examples
+module directory for tests.
+
+Also, importantly, if your test site has its own URL, you'll need to supply that
+with the `--url` option. For instance, under MAMP, you must specify
+`--url http://localhost:8888/`.
+
+You can also use `--concurrency` to speed up the test run, and `--browser` to
+see detailed test results in a web browser instead of just text output in the
+terminal.
+
+	$ php ./core/scripts/run-tests.sh --browser --concurrency 10 --url http://localhost:8888/ --directory modules/examples
+
+This should run all the tests present in Examples. If you add a test and it
+doesn't appear in the list of tests to run, then you'll need to double-check
+that it's in the proper test namespace and that the class name (and thus the
+file name) ends in Test.
 
-What Tests Should An Example Project Have?
+What Tests Should An Example Module Have?
 ------------------------------------------
 
 Examples has a checklist for each module:
diff --git a/config_entity_example/config_entity_example.links.action.yml b/config_entity_example/config_entity_example.links.action.yml
index 9310d40..c5e7858 100644
--- a/config_entity_example/config_entity_example.links.action.yml
+++ b/config_entity_example/config_entity_example.links.action.yml
@@ -11,4 +11,5 @@ config_entity_example.list_action:
   title: 'List Robots'
   appears_on:
     - entity.robot.add_form
-    - entity.robot.edit_form
+    - entity.robot.edit
+    - entity.robot.delete
diff --git a/config_entity_example/src/Tests/ConfigEntityExampleTest.php b/config_entity_example/src/Tests/ConfigEntityExampleTest.php
index 15ffc4c..314573e 100644
--- a/config_entity_example/src/Tests/ConfigEntityExampleTest.php
+++ b/config_entity_example/src/Tests/ConfigEntityExampleTest.php
@@ -139,43 +139,6 @@ class ConfigEntityExampleTest extends WebTestBase {
     $this->drupalGet('/examples/config-entity-example');
     $this->assertText($robby_label);
     $this->assertText($robby_machine_name);
-
-    // 6) Verify that required links are present on respective paths.
-    $this->assertLinkByHref('/examples/config-entity-example/add');
-    $this->assertLinkByHref('/examples/config-entity-example/manage/robby_machine_name');
-    $this->assertLinkByHref('/examples/config-entity-example/manage/robby_machine_name/delete');
-
-    // Verify links on Add Robot.
-    $this->drupalGet('/examples/config-entity-example/add');
-    $this->assertActionButton('examples/config-entity-example');
-
-    // Verify links on Edit Robot.
-    $this->drupalGet('/examples/config-entity-example/manage/robby_machine_name');
-    $this->assertLinkByHref('/examples/config-entity-example/manage/robby_machine_name/delete');
-    $this->assertActionButton('examples/config-entity-example');
-
-    // Verify links on Delete Robot.
-    $this->drupalGet('/examples/config-entity-example/manage/robby_machine_name/delete');
-    // List page will be the destination of the cancel link.
-    $cancel_button = $this->xpath(
-      '//a[@id="edit-cancel" and contains(@href, :path)]',
-      [':path' => '/examples/config-entity-example']
-    );
-    $this->assertEqual(count($cancel_button), 1, 'Found cancel button linking to list page.');
-  }
-
-  /**
-   * Wrap an assertion for the action button.
-   *
-   * @param string $path
-   *   Drupal path to a page.
-   */
-  protected function assertActionButton($path) {
-    $button_element = $this->xpath(
-      '//a[contains(@class, "button-action") and contains(@data-drupal-link-system-path, :path)]',
-      [':path' => $path]
-    );
-    $this->assertEqual(count($button_element), 1, 'Found action button for path: ' . $path);
   }
 
 }
diff --git a/node_type_example/config/install/core.entity_view_display.node.basic_content_type.default.yml b/node_type_example/config/install/core.entity_view_display.node.basic_content_type.default.yml
deleted file mode 100644
index e5977fc..0000000
--- a/node_type_example/config/install/core.entity_view_display.node.basic_content_type.default.yml
+++ /dev/null
@@ -1,26 +0,0 @@
-langcode: en
-status: true
-dependencies:
-  config:
-    - field.field.node.basic_content_type.body
-    - node.type.basic_content_type
-  module:
-    - text
-    - user
-  enforced:
-    module:
-      - node_type_example
-id: node.basic_content_type.default
-targetEntityType: node
-bundle: basic_content_type
-mode: default
-content:
-  body:
-    label: hidden
-    type: text_default
-    weight: 101
-    settings: {  }
-    third_party_settings: {  }
-  links:
-    weight: 100
-hidden: {  }
diff --git a/node_type_example/config/install/core.entity_view_display.node.locked_content_type.default.yml b/node_type_example/config/install/core.entity_view_display.node.locked_content_type.default.yml
deleted file mode 100644
index b0e6b6a..0000000
--- a/node_type_example/config/install/core.entity_view_display.node.locked_content_type.default.yml
+++ /dev/null
@@ -1,26 +0,0 @@
-langcode: en
-status: true
-dependencies:
-  config:
-    - field.field.node.locked_content_type.body
-    - node.type.locked_content_type
-  module:
-    - text
-    - user
-  enforced:
-    module:
-      - node_type_example
-id: node.locked_content_type.default
-targetEntityType: node
-bundle: locked_content_type
-mode: default
-content:
-  body:
-    label: hidden
-    type: text_default
-    weight: 101
-    settings: {  }
-    third_party_settings: {  }
-  links:
-    weight: 100
-hidden: {  }
diff --git a/node_type_example/src/Tests/NodeTypeExampleTest.php b/node_type_example/src/Tests/NodeTypeExampleTest.php
index 93cd666..6b104d6 100644
--- a/node_type_example/src/Tests/NodeTypeExampleTest.php
+++ b/node_type_example/src/Tests/NodeTypeExampleTest.php
@@ -117,36 +117,4 @@ class NodeTypeExampleTest extends WebTestBase {
     $this->assertTrue($node, 'Node found in database.');
   }
 
-  /**
-   * Test that all fields are displayed when content is created.
-   */
-  public function testNodeCreation() {
-    // Login content creator.
-    $this->drupalLogin(
-      $this->drupalCreateUser([
-        'create basic_content_type content',
-        'create locked_content_type content',
-      ])
-    );
-
-    // Create random strings to insert data into fields.
-    $title = 'Test title.';
-    $body = 'Test body.';
-    $edit = [];
-    $edit['title[0][value]'] = $title;
-    $edit['body[0][value]'] = $body;
-
-    // Create a basic_content_type content.
-    $this->drupalPostForm('/node/add/basic_content_type', $edit, t('Save'));
-    // Verify all fields and data of created content is shown.
-    $this->assertText($title);
-    $this->assertText($body);
-
-    // Create a locked_content_type content.
-    $this->drupalPostForm('/node/add/locked_content_type', $edit, t('Save'));
-    // Verify all fields and data of created content is shown.
-    $this->assertText($title);
-    $this->assertText($body);
-  }
-
 }