Update README.md

Author: lmbek

README.md

@@ -36,60 +36,62 @@ Then the Go api is being developed and customized by you together with the front
 
 ## How to use (with go get)
 first run the following in CMD (with go installed) <br><br>
-<code>go get github.com/lmbek/gobek</code><br><br>
+The Go package:
+
+    go get github.com/lmbek/gobek
+<br><br>
 Example: how to add framework to main.go<br>
-<pre>
-//go:generate ./bin/windows/go-packager/GoPackager.exe
-// go generate
-// go build -ldflags -H=windowsgui -o NewProjectName.exe
-
-// ** Generating and Building **
-// The above is the generate commands to add icon and manifest to binary,
-// and the build command
-// NOTE: GoPackager.exe is a modified version of goversioninfo (https://github.com/josephspurrier/goversioninfo).
-// You can compile your own GoPackager.exe at ./bin/windows/go-packager by go building the main.go file
-
-// ** Reason Of Framework Explained **
-// This application is meant to find a port and launch a frontend in chrome (windows) or chromium (linux).
-// Meanwhile, it will open a http localhost backend with an api.
-// The API package at ./backend/api/ can be replaced to fit another application,
-// if the framework is to be used for other applications.
-// It is important to note, that the system will require a frontend directory and a data directory,
-// when the application is tested and released, these will also need to be managed (other applications can be put in)
-// This framework is very open-source, since when released to users, the users can modify the frontend files.
-// However, the backend can be kept as binary, but sent to users if they later want to modify it,
-// for example users must be able to modify the application backend, and replace the binary with the modified version.
-
-package main
-
-import (
-	"fmt"
-	"github.com/lmbek/gobek"
-	"os"
-)
-
-// For windows, we need an organisation name and project name
-var organisationName = "NewOrganisationName" // put in organisation name
-var projectName = "NewProjectName"           // put in project name
-var chromeLauncher = gobek.ChromeLauncher{
-	Location:                os.Getenv("programfiles") + "\\Google\\Chrome\\Application\\chrome.exe",
-	FrontendInstallLocation: os.Getenv("localappdata") + "\\Google\\Chrome\\InstalledApps\\" + organisationName + "\\" + projectName,
-}
-var chromiumLauncher = gobek.ChromiumLauncher{
-	Location: "/var/lib/snapd/desktop/applications/chromium_chromium.desktop",
-}
-var frontendPath = "./frontend" // this should be set to where frontend files is (frontend folder: html, css, javascript...)
-func main() {
-	err := gobek.StartDefault(frontendPath, chromeLauncher, chromiumLauncher)
-	if err != nil {
-		fmt.Println(err)
+	
+ 	//go:generate ./bin/windows/go-packager/GoPackager.exe
+	// go generate
+	// go build -ldflags -H=windowsgui -o NewProjectName.exe
+	
+	// ** Generating and Building **
+	// The above is the generate commands to add icon and manifest to binary,
+	// and the build command
+	// NOTE: GoPackager.exe is a modified version of goversioninfo (https://github.com/josephspurrier/goversioninfo).
+	// You can compile your own GoPackager.exe at ./bin/windows/go-packager by go building the main.go file
+	
+	// ** Reason Of Framework Explained **
+	// This application is meant to find a port and launch a frontend in chrome (windows) or chromium (linux).
+	// Meanwhile, it will open a http localhost backend with an api.
+	// The API package at ./backend/api/ can be replaced to fit another application,
+	// if the framework is to be used for other applications.
+	// It is important to note, that the system will require a frontend directory and a data directory,
+	// when the application is tested and released, these will also need to be managed (other applications can be put in)
+	// This framework is very open-source, since when released to users, the users can modify the frontend files.
+	// However, the backend can be kept as binary, but sent to users if they later want to modify it,
+	// for example users must be able to modify the application backend, and replace the binary with the modified version.
+	
+	package main
+	
+	import (
+		"fmt"
+		"github.com/lmbek/gobek"
+		"os"
+	)
+	
+	// For windows, we need an organisation name and project name
+	var organisationName = "NewOrganisationName" // put in organisation name
+	var projectName = "NewProjectName"           // put in project name
+	var chromeLauncher = gobek.ChromeLauncher{
+		Location:                os.Getenv("programfiles") + "\\Google\\Chrome\\Application\\chrome.exe",
+		FrontendInstallLocation: os.Getenv("localappdata") + "\\Google\\Chrome\\InstalledApps\\" + organisationName + "\\" + projectName,
+	}
+	var chromiumLauncher = gobek.ChromiumLauncher{
+		Location: "/var/lib/snapd/desktop/applications/chromium_chromium.desktop",
+	}
+	var frontendPath = "./frontend" // this should be set to where frontend files is (frontend folder: html, css, javascript...)
+	func main() {
+		err := gobek.StartDefault(frontendPath, chromeLauncher, chromiumLauncher)
+		if err != nil {
+			fmt.Println(err)
+		}
 	}
-}
-
-</pre>
 Please do note however that using the main.go from the gobek-example project is recommended
 ## How to test
-<code>go test ./tests/...</code>
+
+	go test ./tests/...
 
 ## How to run
 make your own main.go by following https://github.com/lmbek/gobek-example
@@ -98,4 +100,5 @@ make your own main.go by following https://github.com/lmbek/gobek-example
 Use something like goversioninfo: https://github.com/josephspurrier/goversioninfo
 
 ## How to build
-<code>go build -ldflags -H=windowsgui -o NewProjectName.exe</code>
+
+	go build -ldflags -H=windowsgui -o NewProjectName.exe