d updated markdown snippets

Author: actions-user

approvaltests/docs/README.md

@@ -7,6 +7,7 @@
 
   * [Features](#features)
   * [How Tos](#how-tos)
+  * [Reference](#reference)
   * [Configuration](#configuration)
   * [Main concepts for ApprovalTests](#main-concepts-for-approvaltests)<!-- endToc -->
 

approvaltests/docs/reference/Naming.md

@@ -5,10 +5,14 @@
 <!-- toc -->
 ## Contents
 
-  * [Paintables](#paintables)
-    * [Why](#why)
-  * [How To](#how-to)
-    * [create an animated gif](#create-an-animated-gif)<!-- endToc -->
+  * [Additional Naming Parameters](#additional-naming-parameters)
+  * [How to do this](#how-to-do-this)
+    * [The old way](#the-old-way)
+    * [The new way](#the-new-way)
+      * [Adding to an existing scenario](#adding-to-an-existing-scenario)
+  * [Parameterized Tests](#parameterized-tests)
+  * [Only running on a specific machine](#only-running-on-a-specific-machine)
+  * [Capturing approvals from CI](#capturing-approvals-from-ci)<!-- endToc -->
 
 ## Additional Naming Parameters
 
@@ -28,23 +32,47 @@ The way this is handled is through the naming factories. This will give you appr
 ### The old way
 There is a global namer factory that can be accessed with a try/catch. While this way works, it is not thread-safe
 and can cause trouble when running tests in parallel. Here is an example of how to do it:
-snippet: namer_factory_example
+<!-- snippet: namer_factory_example -->
+<a id='snippet-namer_factory_example'></a>
+```java
+try (NamedEnvironment namer = NamerFactory.withParameters("title", "chapter"))
+{
+  Approvals.verify("data");
+}
+```
+<sup><a href='/approvaltests-tests/src/test/java/org/approvaltests/namer/NamerFactoryForOptionsTest.java#L27-L32' title='Snippet source file'>snippet source</a> | <a href='#snippet-namer_factory_example' title='Start of snippet'>anchor</a></sup>
+<!-- endSnippet -->
 
 This will result in a file named:
 `ClassName.methodName.firstString.secondString.approved.txt`
 
 ### The new way
 With the addition of `Options` you can now set additional naming information in a thread-safe way. Here is an example of how to do that:
 
-snippet: additional_information_example
+<!-- snippet: additional_information_example -->
+<a id='snippet-additional_information_example'></a>
+```java
+Approvals.verify("data", Approvals.NAMES.withParameters("title", "chapter"));
+```
+<sup><a href='/approvaltests-tests/src/test/java/org/approvaltests/namer/NamerFactoryForOptionsTest.java#L37-L39' title='Snippet source file'>snippet source</a> | <a href='#snippet-additional_information_example' title='Start of snippet'>anchor</a></sup>
+<!-- endSnippet -->
 
 This will result in a file named:
 `ClassName.methodName.firstString.secondString.approved.txt`
 
 #### Adding to an existing scenario
 If there is already an `Options` created, you can add to it using the `.and` keyword. Here is an example:
 
-snippet: options_and
+<!-- snippet: options_and -->
+<a id='snippet-options_and'></a>
+```java
+Options options = Approvals.NAMES.asOsSpecificTest().and(Approvals.NAMES::asMachineNameSpecificTest);
+ApprovalNamer namer = options.forFile().getNamer();
+String name = namer.getApprovedFile(".txt").getName();
+assertEquals("NamerFactoryForOptionsTest.testMachineSpecificTest.Mac_OS_X.lars-mbp-14.approved.txt", name);
+```
+<sup><a href='/approvaltests-tests/src/test/java/org/approvaltests/namer/NamerFactoryForOptionsTest.java#L46-L51' title='Snippet source file'>snippet source</a> | <a href='#snippet-options_and' title='Start of snippet'>anchor</a></sup>
+<!-- endSnippet -->
 
 This will result in a file named: 
 `ClassName.methodName.OSName.machineName.approved.txt`