Updated README file to be more descriptive (#141)

* Group 12 added cat command after container is created

* making README more descriptive

---------

Co-authored-by: bmsmcgee <98934884+bmsmcgee@users.noreply.github.com>
Co-authored-by: Garth Johnson <growlf@thenetyeti.com>

.devcontainer/devcontainer.json

@@ -41,7 +41,7 @@
 	// "forwardPorts": [],
     "forwardPorts": [
 		8000
-	]
+	],
 
 	// Uncomment the next line if you want start specific services in your Docker Compose config.
 	// "runServices": [],
@@ -50,7 +50,7 @@
 	// "shutdownAction": "none",
 
 	// Uncomment the next line to run commands after the container is created.
-	// "postCreateCommand": "cat /etc/os-release",
+	"postCreateCommand": "cat /etc/os-release"
 
 	// Configure tool-specific properties.
 	// "customizations": {},

README.md

@@ -29,7 +29,7 @@ You can find more at:
 
 ## Batteries included
 
-### Custom Shell
+### Custom Shell 
 
 Using the `docker-compose.yml` file (included) makes certain tasks easier.  For example, opening a self-removing ZShell instance can be done lke so:
 
@@ -41,13 +41,13 @@ Using `tcpdump` can either be done from within a shell of the toolbox container,
 
     docker run --rm -it --net=host ghcr.io/growlf/toolbox sudo tcpdump
 
-### Running scripts and commands
+### Running scripts and commands 
 
 You can also run arbitrary commands and scripts directly from the commandline like so:
 
     docker compose run --rm -it app1 ./test_net.sh
 
-## Invoke
+## Using the Invoke Command
 
 This image implements [Python Invoke](https://www.pyinvoke.org/), for managing shell-oriented subprocesses and organizing executable Python code into CLI-invokable tasks. There are a few basic tasks defined as examples already.
 
@@ -86,3 +86,4 @@ Use the `portainer-compose.yml` file and modify to your hearts content.
 - https://pypi.org/project/portscan/
 - https://docs.pyinvoke.org/en/stable/
 - https://docker-py.readthedocs.io/en/stable/
+