adding pr suggestions to docs improvements

website/source/docs/post-processors/manifest.html.md

@@ -50,11 +50,11 @@ An example manifest file looks like:
     {
       "name": "docker",
       "builder_type": "docker",
-      "build_time": 1507235854,
+      "build_time": 1507245986,
       "files": [
         {
           "name": "packer_example",
-          "size": 387501056
+          "size": 102219776
         }
       ],
       "artifact_id": "Container",
@@ -64,3 +64,41 @@ An example manifest file looks like:
   "last_run_uuid": "6d5d3185-fa95-44e1-8775-9e64fe2e2d8f"
 }
 ```
+
+If I run the build again, my new build will be added to the manifest file rather than replacing it, so you can always grab specific builds from the manifest by uuid.
+
+The mainfest above was generated from this packer.json:
+```
+{
+  "builders": [
+    {
+      "type":        "docker",
+      "image":       "ubuntu:latest",
+      "export_path": "packer_example",
+      "run_command": [ "-d", "-i", "-t", "--entrypoint=/bin/bash", "{{.Image}}" ]
+    }
+  ],
+    "provisioners": [
+    {
+      "type": "shell",
+      "inline": "mkdir /Setup"
+    },
+    {
+      "type": "file",
+      "source": "../scripts/dummy_bash.sh",
+      "destination": "/Setup"
+    },
+    {
+      "type": "shell",
+      "inline":["ls -alh /Setup/"]
+    }
+  ],
+  "post-processors": [
+    {
+      "type": "manifest",
+      "output": "manifest.json",
+      "strip_path": true
+    }
+  ]
+}
+```

website/source/intro/getting-started/build-image.html.md

@@ -234,7 +234,15 @@ Now save the following text in a file named `firstrun.json`:
             "instance_type": "t2.micro",
             "region": "us-east-1",
             "secret_key": "{{user `aws_secret_key`}}",
-            "source_ami": "ami-fce3c696",
+            "source_ami_filter": {
+              "filters": {
+              "virtualization-type": "hvm",
+              "name": "ubuntu/images/*ubuntu-xenial-16.04-amd64-server-*",
+              "root-device-type": "ebs"
+              },
+              "owners": ["099720109477"],
+              "most_recent": true
+            },
             "ssh_username": "ubuntu",
             "type": "amazon-ebs"
         }
@@ -247,8 +255,10 @@ Now save the following text in a file named `firstrun.json`:
         },
         {
             "type": "shell",
-            "inline":["ls -al /home/ubuntu",
-                      "cat /home/ubuntu/welcome.txt"]
+            "inline":[
+                "ls -al /home/ubuntu",
+                "cat /home/ubuntu/welcome.txt"
+            ]
         },
         {
             "type": "shell",
@@ -260,7 +270,7 @@ Now save the following text in a file named `firstrun.json`:
 
 and to build, run `packer build firstrun.json`
 
-Note that this example provides a `source_ami` instead of a `source_ami_filter` -- this means the example may be out of date by the time you try to use it, but it is provided here so you can see what it looks like to use an ami by name.
+Note that if you wanted to use a `source_ami` instead of a `source_ami_filter` it might look something like this: `"source_ami": "ami-fce3c696",`
 
 Your output will look like this: 
 
@@ -303,7 +313,7 @@ amazon-ebs output will be in this color.
 
 ### A windows example
 
-Note that this uses a larger instance.  You will be charged for it.
+Note that this uses a larger instance.  You will be charged for it. Also keep in mind that using windows AMIs incurs a fee that you don't get when you use linux AMIs.
 
 You'll need to have a boostrapping file to enable ssh or winrm; here's a basic example of that file.
 
@@ -349,8 +359,11 @@ The first example, `inline`, allows you to provide short snippets of code, and w
 Here's an example of a `sample_script.ps1` that will work with the environment variables we will set in our packer config; copy the contents into your own `sample_script.ps1` and provide the path to it in your packer config:
 
 ```
-Write-Output("PACKER_BUILD_NAME is automatically set for you, or you can set it in your builder variables; the default for this builder is: " + $Env:PACKER_BUILD_NAME )
-Write-Output("Remember that escaping variables in powershell requires backticks; for example VAR1 from our config is " + $Env:VAR1 )
+Write-Output("PACKER_BUILD_NAME is automatically set for you,)
+Write-Output("or you can set it in your builder variables; )
+Write-Output("the default for this builder is: " + $Env:PACKER_BUILD_NAME )
+Write-Output("Remember that escaping variables in powershell requires backticks: )
+Write-Output("for example, VAR1 from our config is " + $Env:VAR1 )
 Write-Output("Likewise, VAR2 is " + $Env:VAR2 )
 Write-Output("and VAR3 is " + $Env:VAR3 )
 ```