updated spec

Author: scmacdon

javav2/example_code/neptune/src/main/java/com/example/neptune/scenerio/NeptuneActions.java

@@ -517,7 +517,13 @@ public CompletableFuture<String> createSubnetGroupAsync(String groupName) {
 
         // Get the Amazon Virtual Private Cloud (VPC) where the Neptune cluster and resources will be created
         String vpcId = getDefaultVpcId();
+        logger.info("VPC is : " + vpcId);
+
         List<String> subnetList = getSubnetIds(vpcId);
+        for (String subnetId : subnetList) {
+            System.out.println("Subnet group:" +subnetId);
+        }
+
         CreateDbSubnetGroupRequest request = CreateDbSubnetGroupRequest.builder()
                 .dbSubnetGroupName(groupName)
                 .dbSubnetGroupDescription("Subnet group for Neptune cluster")

javav2/example_code/neptune/src/main/java/com/example/neptune/scenerio/NeptuneScenario.java

@@ -29,9 +29,9 @@ public static void main(String[] args) {
                     clusterName     - The unique identifier for the Neptune DB cluster.
                     dbInstanceId    - The identifier for a specific Neptune DB instance within the cluster.
                 """;
-        String subnetGroupName = "neptuneSubnetGroup58";
-        String clusterName = "neptuneCluster58";
-        String dbInstanceId = "neptuneDB58";
+        String subnetGroupName = "neptuneSubnetGroup65";
+        String clusterName = "neptuneCluster65";
+        String dbInstanceId = "neptuneDB65";
 
         logger.info("""
                    Amazon Neptune is a fully managed graph 

scenarios/basics/neptune/SPECIFICATION.md

@@ -10,7 +10,7 @@ Finally this scenario demonstrates how to clean up resources. Its purpose is to
 
 Here is more context on when it's a good idea to use the `NeptuneAsyncClient`:
 
-1. **Dynamic Resource Provisioning**: The `NeptuneAsyncClient` can be particularly useful when you need to dynamically create, update, or delete Neptune resources as part of your application's functionality. This could be useful in scenarios such as:
+1. **Dynamic Resource Provisioning**: The `NeptuneAsyncClient` can be particularly useful when you need to dynamically create, update, or delete Neptune resources as part of your application's functionality. This could be useful in use cases such as:
 
    - **Multi-tenant Applications**: If you're building a SaaS application that needs to provision Neptune instances on-demand, the `NeptuneAsyncClient` can help you automate this process programmatically.
    - **Ephemeral Environments**: When you need to spin up and tear down Neptune resources as part of your CI/CD pipeline or within a Lambda environments, the `NeptuneAsyncClient` can streamline this process.