Merge branch 'MichaelCade:main' into main

Days/day01.md

@@ -2,10 +2,11 @@
 title: '#90DaysOfDevOps - Introduction - Day 1'
 published: false
 description: 90DaysOfDevOps - Introduction
-tags: "devops, 90daysofdevops, learning"
+tags: 'devops, 90daysofdevops, learning'
 cover_image: null
 canonical_url: null
 id: 1048731
+date: '2022-04-17T10:12:40Z'
 ---
 ## Introduction - Day 1 
 

Days/day02.md

@@ -6,6 +6,7 @@ tags: 'devops, 90daysofdevops, learning'
 cover_image: null
 canonical_url: null
 id: 1048699
+date: '2022-04-17T21:15:34Z'
 ---
 ## Responsibilities of a DevOps Engineer 
 

Days/day13.md

@@ -50,7 +50,7 @@ Remember the code we are starting within our application as well [day13_example1
 
 We now need to think about the code to get our output or message to Twitter in the form of a tweet. We are going to be using [go-twitter](https://github.com/dghubble/go-twitter) This is a Go client library for the Twitter API. 
 
-To test this before putting this into our main application, I created a new directory in our `src` folder called go-twitter-bot, issued the `go mod init github.com/michaelcade/go-twitter-bot on the folder which then created a `go.mod` file and then we can start writing our new main.go and test this out. 
+To test this before putting this into our main application, I created a new directory in our `src` folder called go-twitter-bot, issued the `go mod init github.com/michaelcade/go-twitter-bot` on the folder which then created a `go.mod` file and then we can start writing our new main.go and test this out. 
 
 We now need those keys, tokens and secrets we gathered from the Twitter developer portal. We are going to set these in our environment variables. This will depend on the OS you are running: 
 

README.md

@@ -1,10 +1,9 @@
 # 90DaysOfDevOps
 
 <p align="center">
-  <img src="https://github.com/MichaelCade/90DaysOfDevOps/blob/main/logo.png?raw=true" alt="90DaysOfDevOps Logo"/>
+ <img src="logo.png?raw=true" alt="90DaysOfDevOps Logo" width="50%" height="50%" />
 </p>
 
-
 This repository is used to document my journey on getting a better foundational knowledge of DevOps. I will be starting this journey on the 1st January 2022 but the idea is that we take 90 days which just so happens to be January 1st to March 31st. 
 
 The reason for documenting these days is so that others can take something from it and also hopefully enhance the resources.