Corrections after rebase

Signed-off-by: Ian Maddaus <ian.maddaus@progress.com>

content/reusable/md/chef_solo_environments.md

@@ -9,7 +9,7 @@ environment_path '/var/chef-solo/environments'
 
 Environment data looks like the following in JSON:
 
-```javascript
+```json
 {
   "name": "dev",
   "default_attributes": {

content/reusable/md/data_bag_item.md

@@ -4,7 +4,7 @@ by specifying the name of the data bag to which the item belongs and
 then the filename of the data bag item. The only structural requirement
 of a data bag item is that it must have an `id`:
 
-```javascript
+```json
 {
   /* This is a supported comment style */
   // This style is also supported

content/reusable/md/node_attribute_allowlist.md

@@ -39,7 +39,7 @@ The recommended practice is to use `allowed_automatic_attributes` to allow speci
 
 For example, automatic attribute data similar to:
 
-```javascript
+```json
 {
   "filesystem" => {
     "/dev/disk0s2" => {

content/reusable/md/node_attribute_blocklist.md

@@ -39,7 +39,7 @@ The recommended practice is to use `blocked_automatic_attributes` to block attri
 
 For example, automatic attribute data similar to:
 
-```javascript
+```json
 {
   "filesystem" => {
     "/dev/disk0s2" => {

content/reusable/md/node_ctl_attribute.md

@@ -3,7 +3,7 @@ treated as a `normal` attribute. Setting attributes at other precedence
 levels is not possible. For example, attempting to update `override`
 attributes using the `-j` option:
 
-```javascript
+```json
 {
   "name": "dev-99",
   "description": "Install some stuff",
@@ -18,7 +18,7 @@ attributes using the `-j` option:
 
 will result in a node object similar to:
 
-```javascript
+```json
 {
   "name": "maybe-dev-99",
   "normal": {

content/reusable/md/node_ctl_run_list.md

@@ -1,7 +1,7 @@
 Use this option to define a `run_list` object. For example, a JSON file
 similar to:
 
-```javascript
+```json
 "run_list": [
   "recipe[base]",
   "recipe[foo]",

content/reusable/md/node_run_list_format.md

@@ -2,19 +2,19 @@ A run-list must be in one of the following formats: fully qualified,
 cookbook, or default. Both roles and recipes must be in quotes, for
 example:
 
-```javascript
+```json
 "role[NAME]"
 ```
 
 or
 
-```javascript
+```json
 "recipe[COOKBOOK::RECIPE]"
 ```
 
 Use a comma to separate roles and recipes when adding more than one item
 the run-list:
 
-```javascript
+```json
 "recipe[COOKBOOK::RECIPE],COOKBOOK::RECIPE,role[NAME]"
 ```

content/reusable/md/policyfile_lock_json.md

@@ -3,8 +3,9 @@ necessary cookbooks and emits a `Policyfile.lock.json` file that
 describes:
 
 - The versions of cookbooks in use
-- A Hash of cookbook content
+- A hash of cookbook content
 - The source for all cookbooks
+- Attributes included with the Policyfile
 
 A `Policyfile.lock.json` file is associated with a specific policy
 group, which means it is associated with one (or more) nodes that use the same

content/reusable/md/policyfile_lock_json_example.md

@@ -1,6 +1,6 @@
 A `Policyfile.lock.json` file is similar to:
 
-```javascript
+```json
 {
   "revision_id": "288ed244f8db8bff3caf58147e840bbe079f76e0",
   "name": "jenkins",
@@ -31,4 +31,15 @@ A `Policyfile.lock.json` file is similar to:
       "artifactserver": "https://supermarket.chef.io/api/v1/cookbooks/java/versions/1.24.0/download",
       "version": "1.24.0"
     }
+  "default_attributes": {
+    "audit": {
+      "reporter": [
+        "chef-server-automate",
+        "cli"
+      ]
+    }
+  },
+  "override_attributes": {
+
+  },
 ```

content/reusable/md/search_key_nested.md

@@ -12,7 +12,7 @@ card made by the specified vendor.
 
 Consider the following snippet of JSON data:
 
-```javascript
+```json
 {"network":
   [
   //snipped...

content/reusable/md/search_pattern_fuzzy_summary.md

@@ -7,7 +7,7 @@ knife search client "name:boo~"
 where `boo~` defines the fuzzy search pattern. This will return
 something similar to:
 
-```javascript
+```json
 {
   "total": 1,
   "start": 0,

layouts/shortcodes/data_bag_item.md

@@ -4,7 +4,7 @@ by specifying the name of the data bag to which the item belongs and
 then the filename of the data bag item. The only structural requirement
 of a data bag item is that it must have an `id`:
 
-```javascript
+```json
 {
   /* This is a supported comment style */
   // This style is also supported

layouts/shortcodes/node_run_list_format.md

@@ -2,19 +2,19 @@ A run-list must be in one of the following formats: fully qualified,
 cookbook, or default. Both roles and recipes must be in quotes, for
 example:
 
-```javascript
+```json
 "role[NAME]"
 ```
 
 or
 
-```javascript
+```json
 "recipe[COOKBOOK::RECIPE]"
 ```
 
 Use a comma to separate roles and recipes when adding more than one item
 the run-list:
 
-```javascript
+```json
 "recipe[COOKBOOK::RECIPE],COOKBOOK::RECIPE,role[NAME]"
 ```

layouts/shortcodes/search_key_nested.md

@@ -12,7 +12,7 @@ card made by the specified vendor.
 
 Consider the following snippet of JSON data:
 
-```javascript
+```json
 {"network":
   [
   //snipped...

layouts/shortcodes/search_pattern_fuzzy_summary.md

@@ -7,7 +7,7 @@ knife search client "name:boo~"
 where `boo~` defines the fuzzy search pattern. This will return
 something similar to:
 
-```javascript
+```json
 {
   "total": 1,
   "start": 0,