- Added Weglot Javascript initializer in base template
- The placeholder key in this initializer code will be replaced
with the actual key by a weglot gulp task during production
deployment

[Theme rebuild] Weglot integration v1

* An introduction to bash shell programming - part 3

* tech edit

* copy edit

* code fixes

* Copy Edit of In This Section

* Vale fix

…th Linode Object Storage (linode#2921)

* Initial Stub

* Final first draft

* Vale fixes

* In this guide, formatting, and a few other things

- In this guide
- Formatting
- Info about overlapping rules
- How to deny access to a certain set of rules

* tech edit

* Copy edit

* Vale fixes

* Remove mihalis guide that snuck in in last commit

* Redirect the old CLI guide.

* Update index.md

* Update index.md

* Update index.md

* Fixed aliases to redirect to Linode CLI API v4 version.

Currently: Google's top two results for Linode CLI link to both
`platform/api/using-the-linode-cli` and `platform/api/linode-cli`,
respectively.

When an alias exists, hugo will create a directory to
match the alias entry that contains an html file specifying
the canonical URL for the page and a new redirect target.
Since, there is an existing guide in the alias location
(`platform/api/using-the-linode-cli`) aliasing was not working
as expected. Visiting a `platform/api/using-the-linode-cli` still
directed you to the deprecated guide.

For this reason, I renamed the deprecated guide's url to:
`/platform/api/using-the-linode-cli-api-v3/`. I moved all aliases
in the deprecated guide to the current guide. Now, all previous aliases
point to our current version of the guide.

I also changed the deprecated guide's H1 to
"Linode CLI (API v3 - Deprecated)", so it is immediately
visible to users that this guide is *Deprecated*.

Merge Master into Develop (Hotfixes 0.27.1 to 0.27.4)

…uster (linode#2965)

* # This is a combination of 2 commits.
# This is the 1st commit message:

added a note

# This is the commit message linode#2:

removed the trailing space

* rebased

I selected this link and found out that openspf.org has been dead since February 2019. In searching for something comparable that would serve a similar purpose, I found this page https://www.dmarcanalyzer.com/spf/how-to-create-an-spf-txt-record/. 

Though to be fair that page above belongs to a for-profit company, it may be a marketing decision if recommending a third-party tool such as this or mxtoolbox

* File I/O in Go

* Tech Edit

* Copy Edit

* Vale fix

* Misc. copy edits

Update guide H1, title and url to use our retitling rubric
Add missing 'In this guide' links
Reword guide description

* create a cluster caveat notes

* Update copy for LKE cluster region availability and plan types.

* added instructions to enable the service

* small copy edit

Add aliases from the deleted guides to How Linode Billing Works
in case anyone has those links bookmarked.