Merge pull request #313 from HoomanDigital/main

review: PR 308

src/content/Docs/guides/ruby-on-rails-with-sia-and-auth0/index.md

@@ -8,7 +8,7 @@ linkTitle: "Ruby on Rails with Sia and Auth0"
 
 
 
-**Repository**: [ovrclk/akash-on-rails](https://github.com/ovrclk/akash-on-rails)\
+**Repository**: [ovrclk/akash-on-rails](https://github.com/ovrclk/akash-on-rails)
 
 
 This is an example Rails Pinterest clone hosted on Akash. There are a few extra features to make the most of decentralised hosting:

src/content/Docs/index.mdx

@@ -98,7 +98,7 @@ import rocket from "./assets/providers/rocket.svg";
     title="Build a Cloud Provider with Praetor App"
     description="Praetor App provides an easy way to become a cloud provider for Akash Network. You can become a provider using a simplified UI rather than Command-line Interface. Once you become a cloud provider, and if the deployers choose your provider to deploy their application, they pay you in AKT."
     icon={praetor}
-    link="https://docs.praetorapp.com/akash-provider/build-a-cloud-provider"
+    link="/docs/deployments/praetor-app/what-is"
   />
   <Card
     title="Akash Provider FAQ and Guide "

src/content/Docs/providers/build-a-cloud-provider/akash-cloud-provider-build-with-helm-charts/index.md

@@ -652,11 +652,11 @@ helm uninstall akash-provider -n akash-services
 
 #### Overview
 
-> _**NOTE**_ - if you are updating your provider bid script from a previous version use this [bid script migration guide](../../akash-provider-troubleshooting/provider-bid-script-migration-gpu-models.md).
+> _**NOTE**_ - if you are updating your provider bid script from a previous version use this [bid script migration guide](../../../../docs/providers/provider-faq-and-guide/#gpu-provider-troubleshooting).
 
 - If there is a desire to manipulate the provider bid engine, include the `--set bidpricescript` switch . The pricing script used in this switch is detailed in the [Akash Provider Bid Pricing](/docs/providers/build-a-cloud-provider/akash-provider-bid-pricing-calculation/) section of this guide.
 - **Note -** When the provider deployment is created the bid script should return the price in under 5 seconds . If the script does not execute in this time period the following error message will be seen in the provider pod logs. Such a report would suggest that there is an error/issue with script customizations that should be reviewed. Following review and adjustment, uninstall the provider deployment (via helm uninstall) and reinstall.
-- **Note** - there is further discussion on the bid script and deployer address whitelisting in this [section](#step-11---provider-whitelisting-optional).
+- **Note** - there is further discussion on the bid script and deployer address whitelisting in this [section](#step-11---firewall-rule-review).
 
 > _**USDC Stable Payment Support**_ - note that the current, default bid script enables stable payment support on the Akash Provider. Akash deployments using stable payments are taxed at a slightly higher rate than deployments using AKT payment. If you choose not to support stable payments on your provider, remove stable payment support from the default bid script.
 
@@ -728,7 +728,7 @@ akash-provider         	akash-services	28      	2023-09-19 12:25:33.880309778 +0
 
 Create the `ingress-nginx-custom.yaml` file via this step
 
-> _**NOTE**_ - in the default install the dedicated Akash RPC Node used for your provider is reachable only within the Kubernetes cluster. This is done intentionally as this RPC Node is intended for use only by the Akash Provider only. The Provider will have access within the cluster to the RPC Node. This additionally protects the RPC Node from possible DDoS attacks from external parties. If have a need to expose the Provider's RPC Node to the outside world, use the `ingress-nginx-custom.yaml` file included in this [section](#step-8---provider-bid-customization) instead.
+> _**NOTE**_ - in the default install the dedicated Akash RPC Node used for your provider is reachable only within the Kubernetes cluster. This is done intentionally as this RPC Node is intended for use only by the Akash Provider only. The Provider will have access within the cluster to the RPC Node. This additionally protects the RPC Node from possible DDoS attacks from external parties. If have a need to expose the Provider's RPC Node to the outside world, use the `ingress-nginx-custom.yaml` file included in this [section](#step-8---provider-build-via-helm-chart) instead.
 
 ```
 cd ~

src/content/Docs/providers/build-a-cloud-provider/akash-provider-checkup/index.md

@@ -116,7 +116,7 @@ Launch the Akash Console application to complete the sections that follow.
 ![](../../../assets/akashlyticsCreateDeployment.png)
 
 - In our testing we will use the Hello Akash World simple SDL
-- Note - this SDL does not specify any attributes. If the list of bids received from the deployment is large and you would like to reduce the list to isolate a bid from your provider a bit easier, consider attribute use as detailed in this [SDL reference](/docs/providers/akash-audites-atributes#auditor-location-within-the-sdl).
+- Note - this SDL does not specify any attributes. If the list of bids received from the deployment is large and you would like to reduce the list to isolate a bid from your provider a bit easier, consider attribute use as detailed in this [SDL reference](/docs/providers/audited-attributes/#auditor-location-within-the-sdl).
 - Otherwise process with the deployment with no need for change to the Hello Akash World SDL and pause when you reach reach the Create Lease phase of the deployment
 
 ![](../../../assets/akashlyticsHelloWorldSelect.png)
@@ -139,7 +139,7 @@ Launch the Akash Console application to complete the sections that follow.
 
 - A new tab within your browser should launch and Hello Akash World home page should display as demonstrated below
 - Note - the URL will be directed to the Ingress Controller of your provider Kubernetes cluster
-- If this page does not display properly it would indicate an issue with the provider’s Ingress Controller and we should investigate via the [Provider Troubleshooting guide](../../akash-provider-troubleshooting/)
+- If this page does not display properly it would indicate an issue with the provider’s Ingress Controller and we should investigate via the [Provider Troubleshooting guide](/docs/providers/provider-faq-and-guide/#gpu-provider-troubleshooting)
 
 ![](../../../assets/helloWorldHomePage.png)
 
@@ -322,17 +322,17 @@ AKASH_WITHDRAWAL_PERIOD=1h
 
 ## STEP 7 - Additional Verifications
 
-As desired consider additional verifications covered in the [Akash Provider Troubleshooting ](../../akash-provider-troubleshooting/)documentation.
+As desired consider additional verifications covered in the [Akash Provider Troubleshooting ](/docs/providers/provider-faq-and-guide/#gpu-provider-troubleshooting)documentation.
 
 Among the topics covered in the troubleshooting guide that should be considered for your new provider verifications:
 
-- [Provider Lease Verifications and Management](../../akash-provider-troubleshooting/provider-lease-management.md)
-- [Provider Manifest Verifications and Management](../../akash-provider-troubleshooting/provider-manifests.md)
-- [Provider Earnings Review](../../akash-provider-troubleshooting/provider-earnings.md)
+- [Provider Lease Verifications and Management](/docs/providers/provider-faq-and-guide/#provider-lease-management)
+- [Provider Manifest Verifications and Management](/docs/providers/provider-faq-and-guide/#provider-manifests)
+- [Provider Earnings Review](/docs/providers/provider-faq-and-guide/#provider-earnings)
 
 # Contact Technical Support
 
-Please contact Akash technical support for any Provider issues not resolved following the review of our [Provider Checkup](./) and [Provider Troubleshooting](../../akash-provider-troubleshooting/) guides.
+Please contact Akash technical support for any Provider issues not resolved following the review of our [Provider Checkup](./) and [Provider Troubleshooting](/docs/providers/provider-faq-and-guide/#gpu-provider-troubleshooting) guide.
 
 - [Akash Discord Server](https://discord.com/invite/akash) - post questions in the dedicated provider channel where our internal and community experts are ready to assist
-- [Akash Forums](https://forum.akash.network/) - post questions in the Help Desk category for Provider support 
+- [Akash Community Discussions](hhttps://github.com/orgs/akash-network/discussions) - post questions in the `🙏Q&A` category for Provider support 

src/content/Docs/providers/build-a-cloud-provider/gpu-resource-enablement/index.md

@@ -44,7 +44,7 @@ apt autoremove
 
 The `ubuntu-drivers devices` command detects your GPU and determines which version of the NVIDIA drivers is best.
 
-> _**NOTE**_ - the NVIDIA drivers detailed and installed in this section have known compatibility issues with some `6.X` lLinux kernels as discussed [here](https://forums.developer.nvidia.com/t/390-154-driver-no-longer-works-with-kernel-6-0/230959/7). In our experience, when such compatibility issue occur the driver will install with no errors generated but will not functionality properly. If you encounter Linux kernel and NVIDIA driver compatibility issues, consider downgrading the Kernel to the officially supported Ubuntu 22.04 kernel which at the time of this writing is `5.15.0-73`
+> _**NOTE**_ - the NVIDIA drivers detailed and installed in this section have known compatibility issues with some `6.X` Linux kernels as discussed [here](https://forums.developer.nvidia.com/t/390-154-driver-no-longer-works-with-kernel-6-0/230959/7). In our experience, when such compatibility issue occur the driver will install with no errors generated but will not functionality properly. If you encounter Linux kernel and NVIDIA driver compatibility issues, consider downgrading the Kernel to the officially supported Ubuntu 22.04 kernel which at the time of this writing is `5.15.0-73`
 
 ```
 apt install ubuntu-drivers-common
@@ -107,7 +107,7 @@ In some circumstances it has been found that the CUDA Drivers Fabric Manager nee
 apt-get install cuda-drivers-fabricmanager-525
 ```
 
-[Reference](https://docs.akash.network/providers/akash-provider-troubleshooting/gpu-provider-troubleshooting)
+[Reference](/docs/providers/provider-faq-and-guide/#gpu-provider-troubleshooting)
 
 ### Additional References for Node Configurations