updated broken links (CrunchyData#1053)

update links in the documenation that were giving 404 errors. I updated the design link in the configuration.md file. I also updated the pgo cli sntax and examples, design overview, and developing links in the index.md file. I updated the github repository link for contributing and fixed the link for namespace formatting reference on namespace.md and olm.md

Author: ValClarkson

hugo/content/Configuration/configuration.md

@@ -121,7 +121,7 @@ command line flag.
 
 ## Namespace Configuration
 
-The Design [Design](/Design) section of this documentation talks further about
+The Design [Design](/gettingstarted/design) section of this documentation talks further about
 the use of namespaces within the Operator and configuring different
 deployment models of the Operator.
 

hugo/content/Installation/operator-install.md

@@ -31,7 +31,7 @@ The Operator follows a golang project structure, you can create a structure as f
  cd $HOME/odev/src/github.com/crunchydata
  git clone https://github.com/CrunchyData/postgres-operator.git
  cd postgres-operator
-git checkout 4.1.0
+git checkout v4.1.0
 
 
 This creates a directory structure under your HOME directory name *odev* and clones the current Operator version to that structure. 

hugo/content/_index.md

@@ -38,13 +38,13 @@ The Operator is developed and tested on CentOS and RHEL Linux platforms but is k
 ## Documentation
 The following documentation is provided:
 
- - [pgo CLI Syntax and Examples](/operator-cli)
+ - [pgo CLI Syntax and Examples](/operatorcli)
  - [Installation](/installation)
  - [Configuration](/configuration) 
  - [pgo.yaml Configuration](/configuration/pgo-yaml-configuration) 
  - [Security](/security) 
- - [Design Overview](/design) 
- - [Developing](/developer-setup) 
+ - [Design Overview](/gettingstarted/design/designoverview) 
+ - [Developing](/installation/developer-setup) 
  - [Upgrading the Operator](/upgrade)
  - [Contributing](/contributing/documentation-updates)
 

hugo/content/contributing/documentation-updates.md

@@ -17,7 +17,7 @@ If you would like to build the documentation locally, view the
 You can then start the server by running the following commands -
 
 ```
-cd $COROOT/hugo/
+cd $PGOROOT/hugo/
 hugo server
 ```
 

hugo/content/contributing/issues.md

@@ -6,7 +6,7 @@ weight: 902
 ---
 
 
-If you would like to submit an feature / issue for us to consider please submit an to the official [GitHub Repository](ttps://github.com/CrunchyData/crunchy-containers/issues/new/choose).
+If you would like to submit an feature / issue for us to consider please submit an to the official [GitHub Repository](https://github.com/CrunchyData/postgres-operator/issues/new/choose).
 
 If you would like to work the issue, please add that information in the issue so that we can confirm we are not already working no need to duplicate efforts.
 

hugo/content/gettingstarted/Design/namespace.md

@@ -31,7 +31,7 @@ the namespaces which will be *watched* by the Operator.
 The format of the NAMESPACE value is modeled after the following
 document:
 
-https://github.com/operator-framework/operator-lifecycle-manager/blob/master/Documentation/design/operatorgroups.md
+https://github.com/operator-framework/operator-lifecycle-manager/blob/0.12.0/doc/design/operatorgroups.md 
 
 
 ### OwnNamespace Example

hugo/content/gettingstarted/Design/olm.md

@@ -11,7 +11,7 @@ The PostgreSQL Operator supports Red Hat OLM (Operator Lifecycle Manager)
 to a degree starting with the PostgreSQL Operator 4.0 release.
 
 The PostgreSQL Operator supports the different deployment models
-as documented [here](https://github.com/operator-framework/operator-lifecycle-manager/blob/master/Documentation/design/operatorgroups.md)
+as documented [here](https://github.com/operator-framework/operator-lifecycle-manager/blob/0.12.0/doc/design/operatorgroups.md )
 
 The PostgreSQL Operator is available for download in [OperatorHub.io](https://www.operatorhub.io/operator/postgres-operator.v3.5.0)