chore: fix links

Author: stepan662

blog/2022-12-6-benefits-challenges-localization.md

@@ -1,14 +1,9 @@
 ---
 slug: benefits-challenges-software-localization
-
 title: 'Benefits and Challenges of Software Localization'
-
 authors: [mchalupnikova]
-
 image: '/img/blog/mt-tolgee/machine_translation_tolgee.png'
-
 description: 'Software localization can offer many benefits for your software business, including expanding your market reach and increasing customer satisfaction.'
-
 tags: [in-context, localization, i18n, translation]
 ---
 
@@ -65,15 +60,15 @@ However, not all people want to make such an investment and prefer **machine tra
 
 Context plays a crucial role in software localization and is necessary for accurate translation. Even if you hire the best translators, they can make mistakes if they don’t have all the needed information.
 
-**Translators rely significantly on context** as it helps them understand the meaning of the text they are translating. Unfortunately, translators still often receive software strings in spreadsheet form with zero context. To get accurate translations of your app, make sure to provide translators with the necessary context. Context is genuinely a [gamechanger in the software localization.](/blog/context-gamechanger-localization)
+**Translators rely significantly on context** as it helps them understand the meaning of the text they are translating. Unfortunately, translators still often receive software strings in spreadsheet form with zero context. To get accurate translations of your app, make sure to provide translators with the necessary context. Context is genuinejly a [gamechanger in the software localization.](/blog/context-gamechanger-localization)
 
 First, Tolgee can offer context in the form of **automatic screenshots** to provide a visual context for the text that needs to be translated, making it easier to understand the meaning and intent. Second, an [in-context translation feature](/blog/in-context-production) can bring even more value to the whole localization process as it enables to **translate directly in your app** just with one click with all the context needed.
 
 ## 5. Formatting issues
 
 To make your software usable for customers in different regions, it’s not enough to simply translate the text. You must also account for formatting differences and **conventions for writing dates, times, numbers, addresses, and currency**. Hard-coded date, time, or currency formats will cause trouble during the localization process, as languages and countries use different date and time formats.
 
-Tolgee deals with formatting issues using the [ICU (International Components for Unicode)](/platform/icu_message_format) message format. ICU also provides a lot of other helpful functionalities, such as advanced pluralization or selection rules.
+Tolgee deals with formatting issues using the [ICU (International Components for Unicode)](/platform/translation_process/icu_message_format) message format. ICU also provides a lot of other helpful functionalities, such as advanced pluralization or selection rules.
 
 ## 6. Inconsistency of translation
 

blog/2024-03-05-releasing-visual-editor-and-formats-support.mdx

@@ -41,8 +41,7 @@ Tolgee now supports the following formats:
 - [Apple .strings and .stringsdict (for iOS, macOS and other Apple platforms)](/platform/formats/apple_strings)
 - [Android Resources XML](/platform/formats/android_xml)
 - [Flutter ARB](/platform/formats/flutter_arb)
-- [PHP Gettext .po](/platform/formats/php_po)
-- [C/C++ Gettext .po](/platform/formats/c_po)
+- [Gettext .po](/platform/formats/po)
 - [Java (.properties)](/platform/formats/properties)
 
 Convenient plurals editing in the visual editor is supported for all formats as well as placeholders visualization as

src/component/pageComponents/header/EmphasisPageHeader.tsx

@@ -2,17 +2,18 @@ import React from 'react';
 import { FC } from 'react';
 import clsx from 'clsx';
 
-export const PageHeader: FC<{ className?: string; noPadding?: boolean }> = (
-  props
-) => (
+export const PageHeader: FC<{
+  className?: string;
+  noPadding?: boolean;
+  children?: React.ReactNode;
+}> = (props) => (
   <header
     className={clsx(
       'header flex flex-col items-center justify-center mx-3 sm:mx-4',
       !props.noPadding && 'pt-[120px] md:pt-[180px]',
       props.className
     )}
   >
-    {' '}
     {props.children}
   </header>
 );

src/component/pageComponents/header/IWantItButton.tsx

@@ -5,6 +5,7 @@ export const PageHeaderSubtitle: FC<{
   active?: boolean;
   className?: string;
   h1?: boolean;
+  children?: React.ReactNode;
 }> = (props) => {
   const Header = props.h1 ? 'h1' : 'h2';
 

src/component/pageComponents/header/PageHeader.tsx

@@ -6,6 +6,7 @@ export const PageHeaderTitle: FC<{
   active?: boolean;
   className?: string;
   h1?: boolean;
+  children?: React.ReactNode;
 }> = (props) => {
   const Header = props.h1 ? 'h1' : 'h2';
 

src/component/pageComponents/header/PageHeaderSubtitle.tsx

@@ -1,6 +1,6 @@
 import React from 'react';
 import './oss-friends.css';
-import { data } from './data.json';
+import json from './data.json';
 
 import DecoratedLayout from '../../theme/DecoratedLayout';
 import { PageHeader } from '../../component/pageComponents/header/PageHeader';
@@ -23,7 +23,7 @@ export default function OssFriends() {
         </PageHeaderSubtitle>
       </PageHeader>
       <div className="oss-friends--content">
-        {data
+        {json.data
           .filter(({ name }) => name !== 'Tolgee')
           .map(({ name, description, href }, i) => (
             <div key={i} className="oss-friends--friend">