diff --git a/README.md b/README.md
index 2858d60e0e..7a75728823 100644
--- a/README.md
+++ b/README.md
@@ -149,7 +149,7 @@ yarn start
## 📚 More Code Examples
-Head over to [docs/typescript.md](./docs/typescript.md) for more examples.
+Read up more on [Logging](./docs/logging.md) and [User Token](./docs/userToken.md) or visit our [documentation](https://getstream.io/chat/docs/) for more examples.
## ✍️ Contributing
diff --git a/assets/logo.svg b/assets/logo.svg
index 1c68c5cccb..ac2e18775a 100644
--- a/assets/logo.svg
+++ b/assets/logo.svg
@@ -1,16 +1,31 @@
-
-
\ No newline at end of file
+
diff --git a/docs/typescript.md b/docs/typescript.md
deleted file mode 100644
index 118ba59b7c..0000000000
--- a/docs/typescript.md
+++ /dev/null
@@ -1,122 +0,0 @@
-# Typescript (v2.x.x)
-
-The StreamChat client is setup to allow extension of the base types through use of generics when instantiated. The default instantiation has all generics set to `Record`.
-
-```typescript
-StreamChat<{
- attachmentType: AttachmentType;
- channelType: ChannelType;
- commandType: CommandType;
- eventType: EventType;
- messageType: MessageType;
- reactionType: ReactionType;
- userType: UserType;
-}>
-```
-
-Custom types provided when initializing the client will carry through to all client returns and provide intellisense to queries.
-
-**NOTE:** If you utilize the `setAnonymousUser` function you must account for this in your user types.
-
-```typescript
-import { StreamChat } from 'stream-chat';
-// or if you are on commonjs
-const StreamChat = require('stream-chat').StreamChat;
-
-type ChatChannel = { image: string; category?: string };
-type ChatUser1 = { nickname: string; age: number; admin?: boolean };
-type ChatUser2 = { nickname: string; avatar?: string };
-type UserMessage = { country?: string };
-type AdminMessage = { priorityLevel: number };
-type ChatAttachment = { originalURL?: string };
-type CustomReaction = { size?: number };
-type ChatEvent = { quitChannel?: boolean };
-type CustomCommands = 'giphy';
-
-type StreamType = {
- attachmentType: ChatAttachment;
- channelType: ChatChannel;
- commandType: CustomCommands;
- eventType: ChatEvent;
- messageType: UserMessage | AdminMessage;
- reactionType: CustomReaction;
- userType: ChatUser1 | ChatUser2;
-};
-
-// Instantiate a new client (server side)
-// you can also use `new StreamChat()`
-const client = StreamChat.getInstance('YOUR_API_KEY', 'API_KEY_SECRET');
-
-/**
- * Instantiate a new client (client side)
- * Unused generics default to Record
- * with the exception of Command which defaults to string & {}
- */
-const client = StreamChat.getInstance('YOUR_API_KEY');
-```
-
-Query operations will return results that utilize the custom types added via generics. In addition the query filters are type checked and provide intellisense using both the key and type of the parameter to ensure accurate use.
-
-```typescript
-// Valid queries
-// users: { duration: string; users: UserResponse[]; }
-const users = await client.queryUsers({ id: '1080' });
-const users = await client.queryUsers({ nickname: 'streamUser' });
-const users = await client.queryUsers({ nickname: { $eq: 'streamUser' } });
-
-// Invalid queries
-const users = await client.queryUsers({ nickname: { $contains: ['stream'] } }); // $contains is only an operator on arrays
-const users = await client.queryUsers({ nickname: 1080 }); // nickname must be a string
-const users = await client.queryUsers({ name: { $eq: 1080 } }); // name must be a string
-```
-
-**Note:** If you have differing union types like `ChatUser1 | ChatUser2` or `UserMessage | AdminMessage` you can use [type guards](https://www.typescriptlang.org/docs/handbook/advanced-types.html#type-guards-and-differentiating-types) to maintain type safety when dealing with the results of queries.
-
-```typescript
-function isChatUser1(user: ChatUser1 | ChatUser2): user is ChatUser1 {
- return (user as ChatUser1).age !== undefined;
-}
-
-function isAdminMessage(msg: UserMessage | AdminMessage): msg is AdminMessage {
- return (msg as AdminMessage).priorityLevel !== undefined;
-}
-```
-
-Intellisense, type checking, and return types are provided for all queries.
-
-```typescript
-const channel = client.channel('messaging', 'TestChannel');
-await channel.create();
-
-// Valid queries
-// messages: SearchAPIResponse
-const messages = await channel.search({ country: 'NL' });
-const messages = await channel.search({ priorityLevel: { $gt: 5 } });
-const messages = await channel.search({
- $and: [{ priorityLevel: { $gt: 5 } }, { deleted_at: { $exists: false } }],
-});
-
-// Invalid queries
-const messages = await channel.search({ country: { $eq: 5 } }); // country must be a string
-const messages = await channel.search({
- $or: [{ id: '2' }, { reaction_counts: { $eq: 'hello' } }],
-}); // reaction_counts must be a number
-```
-
-Custom types are carried into all creation functions as well.
-
-```typescript
-// Valid
-client.connectUser({ id: 'testId', nickname: 'testUser', age: 3 }, 'TestToken');
-client.connectUser({ id: 'testId', nickname: 'testUser', avatar: 'testAvatar' }, 'TestToken');
-
-// Invalid
-client.connectUser({ id: 'testId' }, 'TestToken'); // Type ChatUser1 | ChatUser2 requires nickname for both types
-client.connectUser({ id: 'testId', nickname: true }, 'TestToken'); // nickname must be a string
-client.connectUser({ id: 'testId', nickname: 'testUser', country: 'NL' }, 'TestToken'); // country does not exist on type ChatUser1 | ChatUser2
-```
-
-## More
-
-- [Logging](./logging.md)
-- [User Token](./userToken.md)