fix typos: capital I in Internet, and remove hyphens

kimtore · kimtore · commit d9741ec0569a · 2024-04-22T09:23:35.000+02:00
diff --git a/docs/explanation/naisdevice.md b/docs/explanation/naisdevice.md
@@ -1,6 +1,6 @@
 # Naisdevice
 
-Naisdevice is a mechanism provided by NAIS, that lets you connect to services not available on the public internet from your machine.
+Naisdevice is a mechanism provided by NAIS, that lets you connect to services not available on the public Internet from your machine.
 
 Examples of such services are:
 
diff --git a/docs/explanation/observability/metrics.md b/docs/explanation/observability/metrics.md
@@ -30,7 +30,7 @@ All applications that have Prometheus scraping enabled will show up in the [defa
 
 ## Metric naming
 
-For metric names we use the internet-standard [Prometheus naming conventions](https://prometheus.io/docs/practices/naming/):
+For metric names we use the Internet standard [Prometheus naming conventions](https://prometheus.io/docs/practices/naming/):
 
 - Metric names should have a (single-word) application prefix relevant to the domain the metric belongs to.
 - Metric names should be nouns in **snake_case**; do not use verbs.
diff --git a/docs/how-to-guides/persistence/redis/create-redis-instance-explicitly.md b/docs/how-to-guides/persistence/redis/create-redis-instance-explicitly.md
@@ -51,7 +51,7 @@ Once the resource is added to the cluster, some additional fields are filled in
 
 | field                   |                                                                                                       |
 |-------------------------|-------------------------------------------------------------------------------------------------------|
-| `projectVpcId`          | Ensures the instance is connected to the correct project VPC and is not available on public internet. |
+| `projectVpcId`          | Ensures the instance is connected to the correct project VPC and is not available on public Internet. |
 | `tags`                  | Adds tags to the instance used for tracking billing in Aiven.                                         |
 | `cloudName`             | Where the Redis instance should run.                                                                  |
 | `terminationProtection` | Protects the instance against unintended termination. Must be set to `false` before deletion.         |
diff --git a/docs/reference/ingress.md b/docs/reference/ingress.md
@@ -1,6 +1,6 @@
 # Ingress traffic
 
-Ingress traffic is traffic that is directed to your application from the internet. This is done by configuring the [`ingresses`][nais-ingress] block in your NAIS application yaml manifest with the domains you want your application to receive traffic from.
+Ingress traffic is traffic that is directed to your application from the Internet. This is done by configuring the [`ingresses`][nais-ingress] block in your NAIS application yaml manifest with the domains you want your application to receive traffic from.
 
 [nais-ingress]: https://doc.nais.io/nais-application/application/#ingresses
 
diff --git a/old/clusters/gcp.md b/old/clusters/gcp.md
@@ -46,16 +46,16 @@ You can control from where you application is reachable by selecting the appropr
 
 | domain             | accessible from                                             | description                                                                                                                   |
 | :----------------- | :---------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------- |
-| ekstern.dev.nav.no | internet                                                    | development ingress for applications exposed to internet. URLs containing `/metrics`, `/actuator` or `/internal` are blocked. |
-| intern.dev.nav.no  | [naisdevice](../device/README.md) and NAV internal networks | development ingress for non-public/internet-facing applications                                                               |
+| ekstern.dev.nav.no | Internet                                                    | development ingress for applications exposed to Internet. URLs containing `/metrics`, `/actuator` or `/internal` are blocked. |
+| intern.dev.nav.no  | [naisdevice](../device/README.md) and NAV internal networks | development ingress for non-public/Internet facing applications                                                               |
 
 
 ### prod-gcp ingresses
 
 | domain        | accessible from                   | description                                                                                                                                                                              |
 | :------------ | :-------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| nav.no        | internet                          | URLs containing `/metrics`, `/actuator` or `/internal` are blocked |
-| intern.nav.no | [naisdevice](../device/README.md) | used by non-public/internet-facing applications \(previously called adeo.no\).                                                                                                           |
+| nav.no        | Internet                          | URLs containing `/metrics`, `/actuator` or `/internal` are blocked |
+| intern.nav.no | [naisdevice](../device/README.md) | used by non-public/Internet facing applications \(previously called adeo.no\).                                                                                                           |
 
 
 You can also learn about [how DNS is configured.](../appendix/ingress-dns.md)
diff --git a/old/nais-application/access-policy.md b/old/nais-application/access-policy.md
@@ -42,7 +42,7 @@ The access policy currently have the following limits:
 
 ## Access Policy vs. Ingress
 
-Access policies are only applied to pod-to-pod communication, and not to ingress traffic. This means that you can still use ingress to expose your application to the internet, and use access policies to control which applications can communicate with your application.
+Access policies are only applied to pod-to-pod communication, and not to ingress traffic. This means that you can still use ingress to expose your application to the Internet, and use access policies to control which applications can communicate with your application.
 
 Outbound requests to ingresses are regarded as external hosts, even if these ingresses exist in the same cluster.
 
diff --git a/old/nais-application/ingress.md b/old/nais-application/ingress.md
@@ -1,6 +1,6 @@
 # Ingress traffic
 
-Ingress traffic is traffic that is directed to your application from the internet. This is done by configuring the [`ingresses`][nais-ingress] block in your NAIS application yaml manifest with the domains you want your application to receive traffic from.
+Ingress traffic is traffic that is directed to your application from the Internet. This is done by configuring the [`ingresses`][nais-ingress] block in your NAIS application yaml manifest with the domains you want your application to receive traffic from.
 
 [nais-ingress]: https://doc.nais.io/nais-application/application/#ingresses
 
diff --git a/old/observability/metrics.md b/old/observability/metrics.md
@@ -167,7 +167,7 @@ Then you have full control of the database and retention.
 
 ## Metric naming
 
-For metric names we use the internet-standard [Prometheus naming conventions](https://prometheus.io/docs/practices/naming/):
+For metric names we use the Internet standard [Prometheus naming conventions](https://prometheus.io/docs/practices/naming/):
 
 * Metric names should have a (single-word) application prefix relevant to the domain the metric belongs to.
 * Metric names should be nouns in **snake_case**; do not use verbs.
diff --git a/old/persistence/open-search.md b/old/persistence/open-search.md
@@ -71,7 +71,7 @@ Once the resource is added to the cluster, some additional fields are filled in
 
 | field                   |                                                                                                       | 
 |-------------------------|-------------------------------------------------------------------------------------------------------|
-| `projectVpcId`          | Ensures the instance is connected to the correct project VPC and is not available on public internet. |
+| `projectVpcId`          | Ensures the instance is connected to the correct project VPC and is not available on public Internet. |
 | `tags`                  | Adds tags to the instance used for tracking billing in Aiven.                                         |
 | `cloudName`             | Where the OpenSearch instance should run.                                                             |  
 | `terminationProtection` | Protects the instance against unintended termination. Must be set to `false` before deletion.         |
diff --git a/old/persistence/redis.md b/old/persistence/redis.md
@@ -104,7 +104,7 @@ Once the resource is added to the cluster, some additional fields are filled in
 
 | field                   |                                                                                                       |
 | ----------------------- | ----------------------------------------------------------------------------------------------------- |
-| `projectVpcId`          | Ensures the instance is connected to the correct project VPC and is not available on public internet. |
+| `projectVpcId`          | Ensures the instance is connected to the correct project VPC and is not available on public Internet. |
 | `tags`                  | Adds tags to the instance used for tracking billing in Aiven.                                         |
 | `cloudName`             | Where the Redis instance should run.                                                                  |
 | `terminationProtection` | Protects the instance against unintended termination. Must be set to `false` before deletion.         |
diff --git a/tenants/nav/explanation/migrating-to-gcp.md b/tenants/nav/explanation/migrating-to-gcp.md
@@ -173,7 +173,7 @@ The ROS analysis for the team's applications need to be updated to reflect any c
     | :--- | :--- |
     | `<app>.intern.dev.nav.no` | `dev-fss` |
     | `<app>.intern.nav.no` | `prod-fss` |
-    | `<app>.nav.no` | internet, i.e. all clusters |
+    | `<app>.nav.no` | Internet, i.e. all clusters |
 
     The application on-premises should _not_ have to use webproxy to reach these ingresses.
 
diff --git a/tenants/nav/explanation/naisdevice.md b/tenants/nav/explanation/naisdevice.md
@@ -1,6 +1,6 @@
 # naisdevice
 
-naisdevice is a mechanism provided by NAIS, that lets you connect to services not available on the public internet from your machine.
+naisdevice is a mechanism provided by NAIS, that lets you connect to services not available on the public Internet from your machine.
 
 Examples of such services are:
 - Access to the NAIS cluster with kubectl
diff --git a/tenants/nav/reference/environments.md b/tenants/nav/reference/environments.md
@@ -14,9 +14,9 @@ We also enumerate the external IPs used by the environments, so that you can pro
 
 | domain | accessible from | 
 | :--- | :--- |
-| ekstern.dev.nav.no | internet | 
+| ekstern.dev.nav.no | Internet | 
 | intern.dev.nav.no  | NAV internal networks (including [naisdevice](../explanation/naisdevice.md))| 
-| ansatt.dev.nav.no  | internet, but only accessible by authenticated humans on compliant devices | 
+| ansatt.dev.nav.no  | Internet, but only accessible by authenticated humans on compliant devices | 
 
 See [explanation for exposing application](../explanation/exposing-application.md) for more information.
 
@@ -32,9 +32,9 @@ See [explanation for exposing application](../explanation/exposing-application.m
 
 | domain | accessible from |
 | :--- | :--- |
-| nav.no | internet |
+| nav.no | Internet |
 | intern.nav.no  | NAV internal networks (including [naisdevice](../explanation/naisdevice.md))| 
-| ansatt.nav.no  | internet, but only accessible by authenticated humans on compliant devices | 
+| ansatt.nav.no  | Internet, but only accessible by authenticated humans on compliant devices | 
 
 See [explanation for exposing application](../explanation/exposing-application.md) for more information.
 
diff --git a/tenants/ssb/reference/environments.md b/tenants/ssb/reference/environments.md
@@ -10,7 +10,7 @@ We also enumerate the external IPs used by the environments, so that you can pro
 
 | domain | accessible from | description |
 | :--- | :--- | :--- |
-| external.staging.ssb.cloud.nais.io | internet | ingress for applications exposed to internet. URLs containing `/metrics`, `/actuator` or `/internal` are blocked. |
+| external.staging.ssb.cloud.nais.io | Internet | ingress for applications exposed to Internet. URLs containing `/metrics`, `/actuator` or `/internal` are blocked. |
 | staging.ssb.cloud.nais.io | [naisdevice](../explanation/naisdevice.md) | ingress for internal applications |
 
 #### External/outbound IPs
@@ -23,7 +23,7 @@ We also enumerate the external IPs used by the environments, so that you can pro
 
 | domain | accessible from | description |
 | :--- | :--- | :--- |
-| external.prod.ssb.cloud.nais.io | internet | ingress for applications exposed to internet. URLs containing `/metrics`, `/actuator` or `/internal` are blocked. |
+| external.prod.ssb.cloud.nais.io | Internet | ingress for applications exposed to Internet. URLs containing `/metrics`, `/actuator` or `/internal` are blocked. |
 | prod.ssb.cloud.nais.io | [naisdevice](../explanation/naisdevice.md) | ingress for internal applications |
 
 #### External/outbound IPs
