Merge pull request #6821 from jddocs/rc-v1.299.0

[Release Candidate] v1.299.0

docs/guides/email/email-services/using-magicspam-email-authentication/index.md

@@ -3,7 +3,7 @@ slug: using-magicspam-email-authentication
 description: "Securing your email server with MagicSpam by using country authentication, IP authentication, source based authentication, and other restrictions."
 keywords: ["magicspam", "email authentication", "email server security"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
-modified: 2021-12-29
+modified: 2024-01-22
 modified_by:
   name: Linode
 published: 2021-12-29
@@ -24,7 +24,7 @@ After a threat actor has compromised your email account, they can gain access to
 
 As an email end user, the consequences of having your email compromised can be very serious. After learning about your behaviors and relationships, threat actors can impersonate you. They can leverage the trust of your business partners,friends, and family. Influence them to transfer money, divulge private information, or even infect their machines with malware. Subsequently as the email administrator, the problems of your customers are your problems as well. Besides, dealing with angry customers with compromised accounts, the fallout from compromised accounts being used to send outbound spam effects your IP reputation negatively. This in turn creates more angry customers whose emails are rejected for delivery by other email servers and a whole new set of problems.
 
-Let’s learn how MagicSpam helps email administrators to avoid such a negative outcome and secure your email servers. If you do not yet have MagicSpam installed, you can deploy Linode's [MagicSpam Marketplace App](https://www.linode.com/marketplace/apps/magicspam/magicspam/).
+Let’s learn how MagicSpam helps email administrators to avoid such a negative outcome and secure your email servers.
 
 ## Country Authentication Restrictions
 

docs/guides/game-servers/create-an-ark-server-on-ubuntu/index.md

@@ -6,12 +6,11 @@ keywords: ["ark survival evolved", "ubuntu", "server"]
 tags: ["ubuntu","game servers"]
 license: '[CC BY-ND 3.0](http://creativecommons.org/licenses/by-nd/3.0/us/)'
 external_resources:
- - '[Deploying an ARK Survival Evolved Server through the Linode Marketplace](/docs/products/tools/marketplace/guides/ark-survival-evolved/)'
  - '[The Official Ark Website](http://www.playark.com/)'
  - '[Dedicated Server Setup on the Official Ark: Survival Evolved Wiki](https://ark.wiki.gg/wiki/Dedicated_server_setup)'
  - '[Console commands on the Official Ark: Survival Evolved Wiki](https://ark.wiki.gg/wiki/Console_commands)'
  - '[Studio Wilpost on Epic Games and Steam crossplay](https://survivetheark.com/index.php?/forums/topic/539019-community-crunch-225-crystal-isles-anniversary-event-epic-games-store-and-more/)'
-modified: 2021-10-18
+modified: 2024-01-22
 modified_by:
   name: Linode
 published: 2016-12-28
@@ -24,12 +23,12 @@ authors: ["Nick Brewer"]
 
 This guide demonstrates how to set up a personal [ARK: Survival Evolved](http://www.playark.com/) server on a Linode Compute Instance running a modern Ubuntu distribution.
 
-{{< note respectIndent=false >}}
-Consider using the Linode Marketplace to quickly and automatically deploy an Ark server on our platform. See [Deploying an ARK Survival Evolved Server through the Linode Marketplace](/docs/products/tools/marketplace/guides/ark-survival-evolved/) for instructions.
-{{< /note >}}
-
 **Supported distributions:** Ubuntu 20.04 and 18.04. Recent non-LTS releases like Ubuntu 21.10, 21.04, and 20.10 should also be supported. Ubuntu 16.04 should still be supported, though that LTS release is no longer receiving free security patches or software updates.
 
+{{< note respectIndent=false title="You will need a PC client for Steam and Epic cross-play" >}}
+There is no cross-play between different platforms (Linux and Xbox, for example). For a PC-based server such as this, you will need the PC client from Steam or Epic Games (see more below about Steam and Epic cross-play).
+{{< /note >}}
+
 ![Create an ARK: Survival Evolved Server on Ubuntu](ark-survival-evolved.png)
 
 ## Before You Begin
@@ -40,10 +39,6 @@ Consider using the Linode Marketplace to quickly and automatically deploy an Ark
 
 1.  To connect to your Ubuntu Ark server, you must have a copy of the [Ark: Survival Evolved](http://www.playark.com/) game client running on a local machine.
 
-{{< note respectIndent=false >}}
-There is no cross-play between different platforms (Linux and Xbox, for example). For a PC-based server such as this, you will need the PC client from Steam or Epic Games (see more below about Steam and Epic cross-play).
-{{< /note >}}
-
 {{< note respectIndent=false >}}
 The steps in this guide require root privileges unless otherwise noted. Be sure to run the steps below as `root` or with the `sudo` prefix. For more information on privileges, see our [Users and Groups](/docs/guides/linux-users-and-groups/) guide.
 {{< /note >}}

docs/guides/linode-writers-formatting-guide/index.md

@@ -5,7 +5,7 @@ keywords: ["style guide", "format", "formatting", "how to write", "write for us"
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 aliases: ['/linode-writers-formatting-guide/','/linode-writers-guide/','/style-guide/']
 published: 2014-01-15
-modified: 2023-11-28
+modified: 2024-01-22
 modified_by:
   name: Linode
 title: Linode Writer's Formatting Guide
@@ -649,7 +649,9 @@ To remain consistent across all of our guides, nested content should be indented
 
 ### Note Shortcode
 
-The **note** shortcode is used to display a note to the reader.
+The **note** shortcode is used to display a note to the reader. Notes can be used to share relevant information that does not fit with the primary content. Example use cases include alternative methodologies, non-critical information, alerts, developer recommendations, and more. **Content included in a note must not be required for the reader to successfully understand or complete a task**.
+
+Below is the **default** (primary) note shortcode with default [parameters](#parameters):
 
 ```file
 {{</* note */>}}
@@ -661,82 +663,85 @@ This is an example note.
 This is an example note.
 {{< /note >}}
 
+**Best practices:**
+- **Be concise.** The shorter the better. Notes can lose their impact when they become too long.
+- **Keep things relevant.** The note should pertain directly to the surrounding paragraph, step, or list item. If the note is an unnecessary interruption to the reader, consider removing the note, moving it to a different section, or placing its contents directly in the surrounding content.
+- **Use notes sparingly.** Notes draw attention away from the surrounding content. Too many notes can distract the reader, result in important information getting lost, and are often unnecessary. Consider the impact too many notes or multiple consecutive notes may have to the reader. Often, some information can be omitted and some information is better suited to be included as part of the surrounding text.
+- **Use descriptive titles.** Customize the title of each note so that the reader can quickly assess if the note is relevant to them.
+- **Can be used for short-lived (nonpermanent) content** *(with some caution)*: In many cases, short-lived content is better suited to notes than being hidden within paragraphs or list items. When adding temporary content to a note, always include the date when the content will be out-of-date (if available) as well as information the reader may need to know after that date. An example of this is beta notices. When a new product comes out, the documentation should mention that the product is available as a beta (and, as such, may not be feature complete or production ready). While a note at the top of the related product pages may be warranted, a note within all of our other guides that reference the product is likely not necessary and may create more complications when we need to remove this information.
+
+**What to avoid:**
+- Lengthy notes.
+- Notes not relevant to the surrounding content.
+- Too many notes relative to surrounding content.
+- Stacking notes (multiple consecutive notes).
+- Generic or non-descriptive titles.
+
 #### Parameters
 
-The shortcode accepts the following parameters:
+When creating a new note, there are multiple parameters to consider pertaining to the type of note, its title, and if it can be expanded/collapsed. While not all parameters are always necessary, all should be taken into account during the note creation process.
 
 | Parameter | Values | Description |
 | -- | -- | -- |
-| `type` | | Identifies the note as one of 4 types: |
-|  | `"secondary"` | A muted note. |
-|  | `"primary"` | (*DEFAULT*) A note or tip related to the surrounding content. This is the default type if no type is specified. |
-|  | `"warning"` | A note to take certain precautions. |
-|  | `"alert"` | An important note that should not be skipped over. |
-| `title` | String | Sets the title of the note. |
+| `type` | `"primary"`, `"secondary"`, `"warning"`, `"alert"` | Identifies the note as one of 4 types: primary, secondary, warning, or alert. See: [Note Types](#note-types) |
+| `title` | String | Sets the title of the note. See: [Titles](#titles) for titling guidelines. |
 | `noTitle` | boolean | Does not apply a default title to the note. Defaults to false. |
-| `isCollapsible` | boolean | Sets the note as collapsible. The note must have a title defined. Defaults to false. |
-| `respectIndent` | boolean | This is only used for older note shortcodes (`{{</* note */>}}`) that have been converted to the newer shortcode. By default, content between the shortcode tags is rendered using `.InnerDeindent`, which allows the shortcode to respect the indentation of any parent elements (such as lists). When set to `false`, `.Inner` is used instead, which does not de-indent the content and does not respect the indentation of parent elements. Defaults to true. |
+| `isCollapsible` | boolean | Sets the note as collapsible. The note must have a title defined. Defaults to false. See: [Collapsible](#collapsible) |
+| `respectIndent` | boolean | Only used for older note shortcodes (`{{</* note */>}}`) that have been converted to the newer shortcode. See: [Indentation](#indentation) |
 
 #### Note Types
 
-There are four unique types of notes:
+There are four unique types of notes: **primary**, **secondary**, **warning**, and **alert**. Each type has specific use cases and varying levels of urgency that should determine the type of note you choose to make. Below are examples of each note type and their use cases:
 
--   **Secondary** (`type="secondary"`, title defaults to "Note")
+-   **Primary** (type is unset or `type="primary"`, title defaults to "Note"): Used for additional related information that does not fit with the rest of the document. Can include alternative suggestions or solutions, developer tips, or general best practices that are not critical to the success of the task at hand.
 
-    {{< note type="secondary" >}}
-    This is an example of a secondary note with inline code (`sudo nano`), a link ([Linode Documentation](/docs/)), and a command shortcode:
-
-    ```command
-    sudo apt update
-    ```
+    {{< note title="Best Practice: Use Passsword Generators" >}}
+    When creating root, user, or other passwords, you can increase security by using a password generator such as [1Password](https://www.1password.com) to create and save complex, encrypted passwords.
     {{< /note >}}
 
--   **Primary** (type is unset or `type="primary"`, title defaults to "Note")
-
-    {{< note >}}
-    This is an example of a primary note with inline code (`sudo nano`), a link ([Linode Documentation](/docs/)), and a command shortcode:
+-   **Secondary** (`type="secondary"`, title defaults to "Note"): Most commonly used in tandem with the [collapsible parameter](#collapsible). **Secondary** notes can include non-critical information, commands, code, or output that may take up too much room or does not require visibility for the success of an action.
 
+    {{< note type="secondary" title="Amsterdam Data Center: Lish SSH Gateway Fingerprints" isCollapsible=true >}}
     ```command
-    sudo apt update
+    RSA 3072 SHA256:/y+83+sA3JdDGkv/KLnIAIXqfgqWfgp5RZ+DCx1T4yU lish-nl-ams.linode.com
+    ECDSA 256 SHA256:iR/He+teo+c7jqr8LzaTikbTlMDdIkIERhJBXdIjO8w lish-nl-ams.linode.com
+    ED25519 256 SHA256:vxF9arB2lYBVP45ZA7t1JEE9w/vthPmzU3a2oOR8O7Y lish-nl-ams.linode.com
     ```
     {{< /note >}}
 
--   **Warning** (`type="warning"`, title defaults to "Warning")
-
-    {{< note type="warning" >}}
-    This is an example of a warning note with inline code (`sudo nano`), a link ([Linode Documentation](/docs/)), and a command shortcode:
+-   **Warning** (`type="warning"`, title defaults to "Warning"): Notices that warn the reader to proceed with caution, including notices for beta programs, warnings of limited resource availability, etc. Not as urgent as alert notes.
 
-    ```command
-    sudo apt update
-    ```
+    {{< note type="warning" title="VPC Beta Notice" >}}
+    VPCs are now publicly available in beta, providing customers with another method of isolating network traffic between Compute Instances (in addition to the [VLANs](/docs/products/networking/vlans/) feature). Not all data centers are currently supported. For more information, review the [Availability](/docs/products/networking/vpc/#availability) section.
     {{< /note >}}
 
--   **Alert** (`type="alert"`, title defaults to "Important")
+-   **Alert** (`type="alert"`, title defaults to "Important"): The most urgent of all note types. **Alert** notes should be used to notify of potential *destructive* actions such as situations resulting in data loss or where there is no undoing what has been done. Anything critical to the success of a task should still be included in the primary content and not solely live in the note.
 
-    {{< note type="alert" >}}
-    This is an example of an alert note with inline code (`sudo nano`), a link ([Linode Documentation](/docs/)), and a command shortcode:
-
-    ```command
-    sudo apt update
-    ```
+    {{< note type="alert" title="Back up files to prevent data loss" >}}
+    Formatting a Block Storage Volume will delete all data stored on that Volume. To prevent data loss, verify that any files you wish to retain have been successfully backed up to another storage device.
     {{< /note >}}
 
-#### Custom Title
+#### Titles
+
+Each note can also have a custom title, which is set using the `title` parameter. Titles can specify or summarize the purpose of the note, as well as help define the authority and urgency of the note in the form of tips, best practices, or calls to attention. **Default titles may also be used, but custom titles are preferred for their additional context.**
+- Example summary titles: "Use a strong password", "The token is valid for 24 hours", "A valid payment method is required"
+- Example tip or best practice titles: "Developer Tip", "Common Practice"
+- Example calls to attention: "Before moving forward", "This may result in data loss"
 
-Each note can also have a custom title, which is set using the `title` parameter.
+**Title casing:**
+- If using a single word or phrase, use title casing. *Preferred.*
+- If using a sentence as your title, use sentence casing. Otherwise, use title casing.
 
 ```file {lang="text"}
-{{</* note title="Custom title" */>}}
-This is an example note with a custom title.
+{{</* note title="Custom titles can be helpful" */>}}
+This is an example note with a helfpful custom title.
 {{</* /note */>}}
 ```
 
-{{< note title="Custom title" >}}
-This is an example note with a custom title.
+{{< note title="Custom titles can be helpful" >}}
+This is an example note with a helpful custom title.
 {{< /note >}}
 
-#### No Title
-
 Additionally, you can specify that the note should have no title by using `noTitle=true`. This causes the default title to not display.
 
 ```file {lang="text"}
@@ -751,22 +756,24 @@ This is an example note with no title.
 
 #### Collapsible
 
-Additionally, a note can also be collapsible by setting `isCollapsible=true` (defaults to false). This hides the body of the note and displays a collapse/expand icon.
+Notes can also be made collapsible by setting `isCollapsible=true` (defaults to false). This hides the body of the note and displays a collapse/expand icon. **Secondary notes** are often used for collapsible notes.
 
 ```file {lang="text"}
-{{</* note title="This is a collapsible note with a custom title" isCollapsible=true */>}}
+{{</* note type="secondary" title="This is a collapsible secondary note with a custom title" isCollapsible=true */>}}
 This content is hidden until the user expands the note.
 {{</* /note */>}}
 ```
 
-{{< note title="This is a collapsible note with a custom title" isCollapsible=true >}}
+{{< note type="secondary" title="This is a collapsible secondary note with a custom title" isCollapsible=true >}}
 This content is hidden until the user expands the note.
 {{< /note >}}
 
 #### Indentation
 
 Content within the opening and closing note shortcode tags must respect the expected indentation of any parent elements, such as list items. Since content within a list is indented (using 4 spaces), the content of a note shortcode must be indented by the same number of spaces.
 
+By default, content between the shortcode tags is rendered using `.InnerDeindent`, which allows the shortcode to respect the indentation of any parent elements (such as lists). When set to `false`, `.Inner` is used instead, which does not de-indent the content and does not respect the indentation of parent elements. Defaults to true.
+
 ```file
 -   First list item.
 

docs/products/compute/compute-instances/plans/dedicated-cpu/index.md

@@ -75,11 +75,9 @@ In many cases, the CI/CD pipeline can become resource-intensive if many new code
 
 Depending on the intensity of demands they place on your Linode, [game servers](/docs/game-servers/) may benefit from a Dedicated CPU. Modern multiplayer games need to coordinate with a high number of clients, and require syncing entire game worlds for each player. If CPU resources are not available, then players will experience issues like stuttering and lag. Below is a short list of popular games that may benefit from a Dedicated CPU:
 
-- [ARK: Survival Evolved](/docs/products/tools/marketplace/guides/ark-survival-evolved/)
 - [Rust](/docs/products/tools/marketplace/guides/rust/)
 - [Minecraft](/docs/products/tools/marketplace/guides/minecraft/)
 - [CS:GO](/docs/products/tools/marketplace/guides/counter-strike-go/)
-- [Team Fortress 2](/docs/products/tools/marketplace/guides/team-fortress-2/)
 
 ### Audio and Video Transcoding